Source-Changes-D archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: putenv/setenv changes
On Sun, Oct 03, 2010 at 09:07:45AM +0200, Alan Barrett wrote:
> > Actually the string must be writeable because POSIX requires you
> > to use the actual string passed to putenv() inside the environment
> > array. All strings in the environment array must be writable.
>
> If you mess with the environment using putenv(const string), then you
> should expect the relevant portion to no longer be writable by your
> program; ...
Yes, but something else might try to write to it.
> ... but the implementation can still guarantee that none of the
> putenv/setenv/getenv functions will write to it.
Which is the case for our "libc" after my change.
Kind regards
--
Matthias Scheler http://zhadum.org.uk/
Home |
Main Index |
Thread Index |
Old Index