Date: Fri, 8 Jun 2001 14:22:22 -0400
Message-Id: <200106081822.OAA18661@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 <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <3B20DE0A.11643.87EA3@localhost> (snowball3@bigfoot.com)
Subject: Re: confstr v2
References: <3B1F7174 DOT 21905 DOT 7E6DAE AT localhost> (snowball3 AT bigfoot DOT com) <3B20DE0A DOT 11643 DOT 87EA3 AT localhost>
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


Do we want to punish *every* program with that logic, just for the off
chance that some program calls setenv and then confstr?  Besides, we
can't prevent a program from calling setenv and then running a program
that calls confstr, which I think is what the standard is thinking
about.

I say we use whatever the current value is, without being paranoid
about the program changing it from under itself.  Any program that
sets $DJDIR had better know what it's doing.