This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: linux libio status
- To: jason at cygnus dot com (Jason Merrill)
- Subject: Re: linux libio status
- From: Joe Buck <jbuck at synopsys dot com>
- Date: Wed, 15 Oct 97 8:51:29 PDT
- Cc: jbuck at synopsys dot com, egcs at cygnus dot com
> >>>>> Joe Buck <jbuck@synopsys.com> writes:
>
> > We need to silence these warnings. For the NULL, I suggest a global
> > s/NULL/0/ in the C++ iostreams headers. There is no reason to write
> > NULL, it is just a source of problems like this (*especially* since
> > we have changed C++ to be strict about void*).
>
> But that won't help user code that uses NULL.
The comp.lang.c++ tells users "don't use NULL in C++ programming",
precisely for this reason.
The only other alternatives I can think of is to force a #define NULL 0,
or do some kind of mini-fixincludes on the existing libio.h header.
(The latter technique could solve the problems with the new lock functions
as well).