From: sandmann AT clio DOT rice DOT edu (Charles Sandmann)
Message-Id: <10110021340.AA16752@clio.rice.edu>
Subject: Re: putenv question
To: djgpp-workers AT delorie DOT com
Date: Tue, 2 Oct 2001 08:40:34 -0500 (CDT)
In-Reply-To: <1002006261.19672.6.camel@bender.falconsoft.be> from "Tim Van Holder" at Oct 02, 2001 09:04:18 AM
X-Mailer: ELM [version 2.5 PL2]
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
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

> Since the POSIX draft standard listed putenv's argument as a non-const
> char*, ...

This is really my question - is there any mention of why POSIX thinks
the string we pass it might be modified ? (which is a scary thought itself).

> I don't really see why it can't be const, but I felt it would be best to
> follow the standard.

Following the standard is best (that's why there are standards...) but
there seems to be extra behavior we don't know about or it's a bug in
their standard?