In article <20101003070745.gc23...@apb-laptoy.apb.alt.za>,
Alan Barrett wrote:
>On Sat, 02 Oct 2010, Christos Zoulas wrote:
>> >I suggest a BUGS section in putenv(3) stating that that the interface
>> >uses non-const char* for compatibility with POSIX brain damage, but the
>> >implementation guar
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 envi
On Sat, 02 Oct 2010, Christos Zoulas wrote:
> >I suggest a BUGS section in putenv(3) stating that that the interface
> >uses non-const char* for compatibility with POSIX brain damage, but the
> >implementation guarantees to treat it as read-only.
>
> Actually the string must be writeable because P
On Sat, Oct 02, 2010 at 11:40:12PM +, Christos Zoulas wrote:
> >I suggest a BUGS section in putenv(3) stating that that the interface
> >uses non-const char* for compatibility with POSIX brain damage, but the
> >implementation guarantees to treat it as read-only.
>
> Actually the string must b
On Sun, Oct 03, 2010 at 12:49:32AM +0200, Alan Barrett wrote:
> I suggest a BUGS section in putenv(3) stating that that the interface
> uses non-const char* for compatibility with POSIX brain damage, but the
> implementation guarantees to treat it as read-only.
There is not such guarantee really.
In article <20101002224932.gb23...@apb-laptoy.apb.alt.za>,
Alan Barrett wrote:
>On Sat, 02 Oct 2010, Matthias Scheler wrote:
>> Modified Files:
>> src/lib/libc/stdlib: putenv.c setenv.c
>>
>> Log Message:
>> Restore binary compatibility with application which use putenv(3) on
>> contant str
