On Mon, Oct 03, 2011 at 03:55:58PM +0000, Joseph S. Myers wrote:
> > That would be better, no? Unless __write is part of the glibc API,
> > which AFAIK it isn't.
>
> It's exported at version GLIBC_2.0 (not GLIBC_PRIVATE) under the comment
> "functions used in inline functions or macros", although I don't actually
> see any such functions or macros in current glibc headers. I think being
> under a public version means you can rely on it staying there.
On the architectures where it has been exported, yes. New architectures
might prune those. But we are talking here about a particular architecture
which had these exported, therefore they will continue to be exported
in the future as well, unless glibc SONAME changes (very unlikely).
Jakub
