Date:	Tue, 30 Jul 1996 08:57:54 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
To:	Charles Sandmann <sandmann AT clio DOT rice DOT edu>
Cc:	djgpp-workers AT delorie DOT com
Subject:	Re: USE_LFN woes
In-Reply-To:	<9607291439.AA14037@clio.rice.edu>
Message-Id:	<Pine.SUN.3.91.960730084638.28847F-100000@is>
Mime-Version:	1.0

On Mon, 29 Jul 1996, Charles Sandmann wrote:

> but checking the environment outside the crt1 initialization for changes
> is an unneeded complication.  Keep it simple.

There are programs out there (like Emacs) that blur the distinction 
between the external and the internal environment in a way that will 
break if changing an environment at runtime won't take an immediate 
effect.  In most cases, you won't need to look at the environment, if the 
`environment_changed' variable didn't change its value.

> I don't see
> any way to support enabling this from DJGPP.ENV since we have already
> expanded the globbed command line by the time we load DJGPP.ENV.  Unless
> someone wants to re-write the crt0_setup_arguments stuff.

The code that sets up arguments will be changed anyway--because we want 
to support long command lines in `system'.  I didn't look at it closely 
yet, but up front I don't see any problem in supporting LFN from 
DJGPP.ENV.

Thanks for the other info.  Yes, it is a small piece of code and easy to 
get done, but I thought that given the amount of problems we had with the 
current version, a little discussion could help to make it done better. 

- Raw text -