Date: Sun, 10 Jun 2001 10:41:56 -0400 Message-Id: <200106101441.KAA11909@envy.delorie.com> X-Authentication-Warning: envy.delorie.com: dj set sender to dj AT envy DOT delorie DOT com using -f From: DJ Delorie To: eliz AT is DOT elta DOT co DOT il CC: djgpp-workers AT delorie DOT com In-reply-to: (message from Eli Zaretskii on Sun, 10 Jun 2001 10:41:59 +0300 (IDT)) Subject: Re: confstr v2 References: Reply-To: djgpp-workers AT delorie DOT com Errors-To: nobody AT delorie DOT com X-Mailing-List: djgpp-workers AT delorie DOT com X-Unsubscribes-To: listserv AT delorie DOT com Precedence: bulk > The Posix draft standard clearly says that the result of confstr should > not depend on the changes to environment variables such as PATH made by > users or applications. I just thought that DJDIR should be treated > similarly. True, but in our case it depends on nothing *but* environment variables, so what can we do? It's going to depend on what the user sets for DJDIR in their environment no matter how careful we are, so given that, I don't think we need to be overly paranoid about what happens to the environment after the user is done fiddling with it. At the very least, implement confstr in C++ and use a global constructor to stash away the value of $DJDIR so programs that never call confstr aren't burdened by the code to save it.