Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!ncar!oddjob!gargoyle!att!pacbell!well!ewhac
From: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Newsgroups: comp.sys.amiga
Subject: Re: Enviroment (was Re: Yea, but can an Amiga Shell do this....)
Message-ID: <6889@well.UUCP>
Date: 22 Aug 88 19:05:30 GMT
References: <8808220455.AA27577@cory.Berkeley.EDU>
Reply-To: ewhac@well.UUCP (Leo 'Bols Ewhac' Schwab)
Organization: The Comic Relief Machine
Lines: 25
Quote: "FACTS!  I WANT FA..  I MEAN INNUENDO!  I WANT INNUENDO!!"  -- Milo

In article <8808220455.AA27577@cory.Berkeley.EDU> dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
>[ ...]  in
>fact, none of the enviroment is in memory if you assign ENV: to your floppy 
>or hard disk.  [ ... ]

	The current implementation of this strikes me as a hack.  ENV: is
created in your Startup-Sequence.  This means that if you boot up with an
old floppy, or simply forget to create ENV:, any program that asks for it
will pop up a "Please insert volume ENV in any drive you stupid klutz."
'SetEnv' is also little more than a front-end for 'copy * ENV:var'.

	Shouldn't ENV: be part of the standard start-up assigns, like LIBS:
or L: or C:?  Or am I getting in on this game too late?

>The only plausable assumption one can really make is that 
>enviroment variables contain ASCII (can we even do that?).
>
	Since the variables are, indeed, files, I don't think you can assume
anything about a "variable's" contents.  Binary environment variables could
be fun, you know...

_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_-_
Leo L. Schwab -- The Guy in The Cape	INET: well!ewhac@ucbvax.Berkeley.EDU
 \_ -_		Recumbent Bikes:	UUCP: pacbell > !{well,unicom}!ewhac
O----^o	      The Only Way To Fly.	      hplabs / (pronounced "AE-wack")
"Work FOR?  I don't work FOR anybody!  I'm just having fun."  -- The Doctor