[Info-vax] Logical names, was: Re: Command Procedure Pipe output to a variable

[Dave Froble]

On 10/9/2021 2:14 PM, Arne Vajhøj wrote:
> On 10/9/2021 4:31 AM, Jan-Erik Söderholm wrote:
>> Den 2021-10-09 kl. 01:06, skrev Lawrence D’Oliveiro:
>>> On Saturday, October 9, 2021 at 7:07:17 AM UTC+13, Simon Clubley wrote:
>>>> On a more serious note, does anyone else wish you could attach a
>>>> comment
>>>> to a logical name definition so that you could see in SHOW LOGICAL
>>>> what the purpose of a logical is ?
>>
>> No, better to keep the comments/documentation for each logical name
>> in the command file where the logical is created.

Agree 110%

> If one knows what COM file defined the logical.
>
> But that is not always obvious.

It had better be, or you've already got a real mess.

>>> What do you know, Unix-style text configuration files usually allow
>>> for ample comments.
>>
>> A "configuration file" is just a file where you setup your configuration.
>>
>> Doesn't matter if that file is read directly by the application or if the
>> file is run at application startup and defining a bunch of logical names
>> that are then used by the application.
>>
>> It is still just a "configuration file". And it can have as many
>> comments/documentation as you like.
>
> If the logical strictly relates to a specific application, then
> locating the startup file is not a problem.
>
> It is the other ones that can be tricky.

Should there be any other ones ????

There is system configuration, which must support the required 
application environment.

There is application environment.

A serious demark should exist between them.

My stomach acid is still active after that remark about storing 
application configuration data in SYSGEN parameters.

:-(

-- 
David Froble                       Tel: 724-529-0450
Dave Froble Enterprises, Inc.      E-Mail: davef at tsoft-inc.com
DFE Ultralights, Inc.
170 Grimplin Road
Vanderbilt, PA  15486