Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!pasteur!ucbvax!hplabs!hp-pcd!hpcvca!charles
From: charles@hpcvca.HP.COM (Charles Brown)
Newsgroups: comp.sys.amiga
Subject: Re: ENV: variables (long)
Message-ID: <5660014@hpcvca.HP.COM>
Date: 12 Sep 88 16:08:18 GMT
References: <374@uwslh.UUCP>
Organization: Hewlett-Packard Co., Corvallis, Oregon
Lines: 22

> One interesting non-Unix OS has 4 levels of variables; 2 on disk, 2
> in memory.  The order search is:

This proposal beats both the AmigaDos ENV: solution and the Unix
solution hands down.

> Global variable names are uppercase, local variables are lowercase.

Is this enforced or is it just a convention?

> 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.

This is so sensible that it's frightening.

> {ames|pyramid}oliveb!tymix!antares!jms  |

Charles Brown