Date:	Fri, 28 Aug 92 10:06:04 EST
From:	kelley AT flowcyt DOT cyto DOT purdue DOT edu (Steve Kelley)
To:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	Environment
Cc:	djgpp AT sun DOT soe DOT clarkson DOT edu
Subject:	gcc environment variables

Jonathan Ryshpan:
    >    I recommend that there be a single environment variable (DJGCC ?) to 
    >    specify the location of the .CFG file.

DJ Delorey:
    or, in the GO32 variable, "env <file>" options.  getenv() can scan
    that also, and go32 could be told to ignore it.

YES YES.  This is an excellent suggestion.  Can I suggest also that
it would be extremely useful even for non-DJGPP programs, and that
we *QUICKLY* try to decide on a name that we could standardize through use?

That way, it would be a little easier to search for the 'environment', if 
we want to; and remember, this file could be writable as well as readable.

To start the ball rolling, I'll suggest 'environ.env' as a default. I won't
try to defend that particular choice, I just want to start using something
that people can agree on.

Steve Kelley        kelley AT flowcyt DOT cyto DOT purdue DOT edu

Purdue University Cytometry Labs        (317) 494-8638 -- voice
B050 Hansen LSRB                        (317) 494-0517 -- fax
West Lafayette, Indiana, 47907          

- Raw text -