Re: Bogus ifdef guard in sys/null.h

[Joerg Sonnenberger <joerg%britannica.bec.de@localhost>]

On Sat, Jul 17, 2010 at 12:16:13PM +0300, Stathis Kamperis wrote:
> POSIX says that both stddef.h and unistd.h shall provide NULL. This
> isn't just a thought experiment. It actually broke a test from here:
> http://www.itl.nist.gov/div897/ctg/posix_form.htm
> 
> Please consider changing it, or explain why it shouldn't.

Both headers provide NULL. I remember certain headers are allowed to
include others to provide the complete API, which would break rather
badly if this behavior was actually allowed.

So let me turn your question back -- why should this behavior be
allowed?

Joerg