Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 30 Apr 2007 21:04:46 -0500 (CDT)
From:      "Sean C. Farley" <sean-freebsd@farley.org>
To:        Andrey Chernov <ache@nagual.pp.ru>
Cc:        freebsd-current@freebsd.org
Subject:   Re: setenv memory leak fix (take 3)
Message-ID:  <20070430205747.G28846@thor.farley.org>
In-Reply-To: <20070427122634.GA32237@nagual.pp.ru>
References:  <20070426195122.P37719@thor.farley.org> <20070427122634.GA32237@nagual.pp.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Apr 2007, Andrey Chernov wrote:

> On Thu, Apr 26, 2007 at 08:10:29PM -0500, Sean C. Farley wrote:
>>  Are there any opinions on having unsetenv() return a value to match
>>  unsetenv() in IEEE Std 1003.1?
>
> There is no much options because we should conform to standards and
> unsetenv() should return int therefore.

I know that unsetenv() can be changed without problems since it has no
return value at the moment.  The others are more difficult but not
impossible.  I see that a mild discussion has occurred on cvs.  :)

Here are both scenarios with my code changes:
BSD[1] (only unsetenv() is updated to return an int.  Easy to change
         back)
POSIX[2] (all *env() functions are updated to reflect POSIX)

Sean
   1. http://www.farley.org/freebsd/tmp/setenv-8/BSD/sysenv.c
   2. http://www.farley.org/freebsd/tmp/setenv-8/POSIX/sysenv.c
-- 
sean-freebsd@farley.org



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070430205747.G28846>