Environment handling broken in /bin/sh with changes to t,set,put}env()

[Andrey Chernov]

On Fri, Jul 13, 2007 at 05:27:58PM -0500, Sean C. Farley wrote:
> Does that mean that environ is untouched or that the environment is
> unchanged?  They seem to use both words (environ and environment) in the
> documentation making me think they are not necessarily the same thing.
> Currently, non-getenv() calls rebuilds the environ array if having never
> been changed before, but the "environment" is "unchanged" if the
> variable does not exist.  Should that not meet that requirement?

IMHO by the environment they means environ contents, not pointers, because 
they say:

"The setenv() function shall update the list of pointers to which environ 
points."

-- 
http://ache.pp.ru/