Date: Sun, 29 Mar 1998 21:26:30 -0500 (EST)
Message-Id: <199803300226.VAA00564@delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.980329132539.14969J-100000@is> (message from Eli
	Zaretskii on Sun, 29 Mar 1998 13:25:59 +0300 (IDT))
Subject: Re: NULL redefined! :(
Precedence: bulk


> IMHO, it is not nice to tell people to put their headers in some
> particular order.

> Or, as the path of least resistance, would it really be so hard for DJGPP to
> change? I know it's against principles and all that, but would it kill us to
> surround each `#define NULL 0' with `#ifndef NULL'?

I don't think DJGPP should cause problems if they're easy to deal with
in a reasonably correct way.  However, in this case, I prefer that
DJGPP headers protect themselves with #undef rather than #ifdef, so
that we also protect ourselves from incompatible definitions (if any).
Thus (to paraphrase) we should have:

#undef NULL
#define NULL 0