From mboxrd@z Thu Jan 1 00:00:00 1970 From: Joe Buck To: jason@cygnus.com (Jason Merrill) Cc: jbuck@synopsys.com, egcs@cygnus.com Subject: Re: linux libio status Date: Wed, 15 Oct 1997 09:15:00 -0000 Message-id: <199710151551.IAA22184@atrus.synopsys.com> References: X-SW-Source: 1997-10/msg00581.html > >>>>> Joe Buck 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).