policy on __libc_*

[Ulrich Drepper]

Roland McGrath <roland@frob.com> writes:

> but it would be nice to know what to expect from the os-independent
> parts of libc.

You are right, that would be nice.  But I really have no time to write
this all down in detail.  I think I've explained on the list a few
times already that the __libc_* names are introduced for cancelation
points since the functions must be intercepted even when called from
inside the libc.  I.e., the __* functions also have to be exported.

-- 
---------------.      drepper at gnu.org  ,-.   1325 Chesapeake Terrace
Ulrich Drepper  \    ,-------------------'   \  Sunnyvale, CA 94089 USA
Cygnus Solutions `--' drepper at cygnus.com   `------------------------