>> >* Add a conforming __unsetenv13() and do function renaming for
>> >  unsetenv(); preserve old symbol with old behavior.
>> >* Make visible setenv() and unsetenv() for 1003.1-2001 feature selection
>> >  macros; resolves PR standards/20479.
>>
>> why __unsetenv13()?  why not __unsetenv16() or __unsetenv17()?  i had
>> always assumed that the numeric suffix on a renamed function was
>> somehow indicative of the last release (or first release) that had the
>> new function...
>
>Yes, but it's the version of the library, libc. libc is at major 12, thus
>in version (major) 13, they will loose the extra numberstuff.

oh, ah.  i get it.  cool.  so i was right, but wrong.  :)

>If they were systemcalls, they'd be based on the kernel version.

okay, cool.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."