This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: linux libio status
- To: Jason Merrill <jason at cygnus dot com>
- Subject: Re: linux libio status
- From: Peter Seebach <seebs at monolith dot solon dot com>
- Date: Wed, 15 Oct 1997 22:16:12 -0500
- cc: egcs at cygnus dot com
In message <u9zpoarh0w.fsf@yorick.cygnus.com>, Jason Merrill writes:
>This is why we have a NULL macro. The gcc stddef.h provides an appropriate
>definition, so we can put
>#undef NULL
>#define __need_NULL
>#include <stddef.h>
>#undef __need_NULL
>somewhere strategic, and that should do the trick.
Well, strictly speaking, I don't think that's correct - I *believe* a
user who has not included <stddef.h> is allowed to assume that not everything
in it is defined. I think an implementation is obliged to have the common
declaration of NULL, if there is one, be in some other header included by
<stddef.h> and friends.
>C89 may not have, but gcc defines it that way.
Well, yeah, but that's not very useful to a person writing code not
exclusively for use with one compiler... :)
-s