This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [Patch] Document __secure_getenv
On 7/11/2012 11:44 AM, Florian Weimer wrote:
> I cannot use the new symbol because that would introduce a dependency on a new libc version.
Use <new name for __secure_getenv> if libc supports it,
otherwise keep using __secure_getenv.
After adding the new interface we can make __secure_getenv
hidden so no new programs can't be linked against it.
We aren't going to make __secure_getenv go away, that
would be bad for all the reasons you state, but be
warned that using functions starting with __ will get
you in trouble.
Just because we don't make __secure_getenv go away
today doesn't mean another __ function won't go away
some other day when the community is faced with
conflicting requirements.
In summary: Please make a new function, and document
that function.
Cheers,
Carlos.
--
Carlos O'Donell
Mentor Graphics / CodeSourcery
carlos_odonell@mentor.com
carlos@codesourcery.com
+1 (613) 963 1026