From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <9607301341.AA14557@clio.rice.edu>
Subject: Re: USE_LFN woes
To: eliz AT is DOT elta DOT co DOT il (Eli Zaretskii)
Date: Tue, 30 Jul 1996 08:41:46 -0600 (CDT)
Cc: djgpp-workers AT delorie DOT com
In-Reply-To: <Pine.SUN.3.91.960730084638.28847F-100000@is> from "Eli Zaretskii" at Jul 30, 96 08:57:54 am
Content-Type: text

> 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 would argue that EMACS is broken (or at least very poorly designed) and
the fixes need to be put there, instead of bloating every single application
developed with DJGPP!  None of the real operating environments I know of
change their file I/O behavior between calls on the basis of an environment
variable, so why add such weirdness in DJGPP?