Path: utzoo!utgpu!water!watmath!clyde!att!rutgers!cbmvax!jesup
From: jesup@cbmvax.UUCP (Randell Jesup)
Newsgroups: comp.sys.amiga
Subject: Re: ENV: variables (long)
Message-ID: <4727@cbmvax.UUCP>
Date: 14 Sep 88 07:13:32 GMT
References: <374@uwslh.UUCP> <5660014@hpcvca.HP.COM>
Reply-To: jesup@cbmvax.UUCP (Randell Jesup)
Organization: Commodore Technology, West Chester, PA
Lines: 16

In article <5660014@hpcvca.HP.COM> charles@hpcvca.HP.COM (Charles Brown) writes:
>> Shell variables are of the form "shell.*" (such as
>> "shell.path=(/usr/bin /usr/local/bin"), which is better than the Unix
>> convention.  Instead of storing compiler options in names like
>> FOOBAROPTS, names like FOOBAR.WIDTH, FOOBAR.LINESPERPAGE, FOOBAR.MODE
>> are possible.  The command "list-var FOOBAR.*" lists only the FOOBAR
>> variables.

	It is suggested that users of ENV: use subdirectories to store
application-specific envirionment variables, instead of global ones, to
cut down on name collisions.  The can be extended in some cases to include
the CLI number or process address as part of the name (useful in scripts,
since <$$> expands to the CLI number).

-- 
Randell Jesup, Commodore Engineering {uunet|rutgers|allegra}!cbmvax!jesup