Hi,
Since there is some noise around this, could we just scream for a while
that code should be fixed but allow it to still work? After some time than
the majority of the buggy code will be fixed we will stick to the std
behavior? IMHO this will be less painful.
rik
Andrey Chernov wrote:
On Tue, May 01, 2007 at 04:02:42AM +0400, Andrey Chernov wrote:
On Mon, Apr 30, 2007 at 06:57:17PM -0400, David Schultz wrote:
I think Alfred is absolutely right, and this is a pretty major
POLA violation.
That's -current for. Do you suggest to wait yet more N years to commit
exact that stuff?
Speaking about POLA, POLA says that valid call to setenv f.e. is in form
setenv("name", "value", 1);
it does not says that hacks like
setenv("name=value", "value", 1);
should be allowed and works.
Moreover, putenv() isn't BSD own function, and was incorrectly implemented
initially in BSD. BSD implementation just violates original POLA for
putenv() all other use.
Insisting to keep bug-to-bug compatibility forever leads to nowhere.
And increase porting efforts greately.
_______________________________________________
[email protected] mailing list
http://lists.freebsd.org/mailman/listinfo/cvs-all
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
