Path: utzoo!attcan!uunet!ndsuvax!ncreed
From: ncreed@ndsuvax.UUCP (Walter Reed)
Newsgroups: comp.sys.amiga
Subject: Re: Shell requests (was Re: Yea, but can an Amiga Shell do this....)
Keywords: <- what a cryptologist speaks with.
Message-ID: <1148@ndsuvax.UUCP>
Date: 22 Aug 88 17:24:20 GMT
References: <1836.AA1836@heimat> <3782@hcr.UUCP> <1877@iscuva.ISCS.COM> <3816@hcr.UUCP>
Reply-To: ncreed@ndsuvax.UUCP (Walter Reed)
Organization: North Dakota State University  Fargo, ND
Lines: 25

In article <3816@hcr.UUCP> edwin@hcrvax.UUCP (Edwin Hoogerbeets) writes:
>Comment: If the shell were to be changed to inherit the environment,
>please use Manx "set" style environment vars. (sounds like a type of
>yoghourt, eh?) I think this is what they are going to be using in 1.3 and
>1.4 and this would be an easy way of exporting the environment while
>remaining upwardly compatible.
Um, no.  1.3 uses a totally different method.  They have an ENV: device
which for now is just a logical Assign to a directory.  Each variable
is a file, with a name of the environment variable.  Since environment
variables are files, think of the info that could be stored in them!
much more versitile than normal Manx/Arp style variables.  One could
write a program that could look at the manx style variables and convert
them to 1.3 style ones and visa versa.  It could run once every 10
seconds or so...  

BTW, I have a shared functions library that has 1.3 compatible getenv
and setenv among other things.  As soon as I get the bugs out I will be
making it available.  It has bindings for both compilers.


-- 
------  Walter Reed  ------   + uunet!ndsuvax!ncreed or ncreed@ndsuvax.BITNET
"There's no point in being    +      or ncreed@plains.NoDak.edu
 grown up if you can't be     +   
 childish sometimes!" Dr. Who + USnAIL: 925 9th Ave W.  West Fargo, ND 58078