Date: Thu, 26 Mar 1998 08:44:26 -0500 (EST)
Message-Id: <199803261344.IAA16430@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il, djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.980326104922.29215D-100000@is> (message from Eli
	Zaretskii on Thu, 26 Mar 1998 10:49:44 +0300 (IDT))
Subject: Re: NULL redefined! :(
Precedence: bulk


> As I understand it, without doing something about that, perfectly
> correct programs trigger errors and fail to compile.  Isn't this
> reason enough to do *something*?

Yes.  It's a good reason to fix the C++ library.  In seven years of
C++ programming at Cabletron, NULL has always been 0 and we've never
had a problem with it, but we've always had problems with other
definitions - including 0L and ((void *)0).

> Let me be sure I understand what you are saying.  Are you saying that
> libstdc++ is the ``third-party library'' which should be changed, and
> that we should complain to its developers and request that they stop
> breaking DJGPP?

DJGPP is the first party; the base system.  The ANSI standard is the
second party, to which DJGPP was written.  The C++ libraries would be
the third party, which in my opinion, should work on a conforming ANSI
platform without needing to change the base system.