Re: Ensuring posix-ness

[Bruno Haible]

Eric Blake wrote:
> > But it is marked as [XSI]. I don't know whether that implies that glibc is
> > right in hiding the declaration, or it should enable it?
>
> Glibc bug.  XSI shading means that a non-XSI implementation need not 
> have crypt by default, but glibc is an XSI implementation, so requesting 
> compliance with POSIX 2008 means that crypt() should be visible in 
> <unistd.h>.  There's no feature macro needed to turn on XSI functions - 
> either you have an XSI system and they are all available by default, or 
> you do not have an XSI system (usually embedded systems) and the system 
> documents that it is not provide XSI.

Thanks for explaining.

> Would you care to raise a bug report against glibc?

Likewise about encrypt() in <unistd.h> and setkey() in <stdlib.h>.

Bruno
-- 
In memoriam Elisabeth von Thadden 
<http://en.wikipedia.org/wiki/Elisabeth_von_Thadden>