X-Authentication-Warning: acp3bf.physik.rwth-aachen.de: broeker owned process doing -bs
Date: Wed, 8 Mar 2000 12:49:44 +0100 (MET)
From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
X-Sender: broeker AT acp3bf
To: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
cc: djgpp-workers AT delorie DOT com
Subject: Re: iso646.h and some questions
In-Reply-To: <Pine.SUN.3.91.1000308133453.7315D-100000@is>
Message-ID: <Pine.LNX.4.10.10003081242250.16372-100000@acp3bf>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp-workers AT delorie DOT com
Errors-To: dj-admin AT delorie DOT com
X-Mailing-List: djgpp-workers AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk

On Wed, 8 Mar 2000, Eli Zaretskii wrote:

> On Wed, 8 Mar 2000, Hans-Bernhard Broeker wrote:
> 
> > Just add the same two lines to wchar.h that are already in all the other
> > ANSI headers that also define NULL (it's defined by half a dozen of
> > them...):
> > 
> > 	#undef NULL
> > 	#define NULL 0
> 
> Won't this make trouble in C++ programs?

Why should it? This is the exact definition found in current DJGPP
headers, already. So if there were trouble to expected from that, C++
programmers would have told us. If memory serves, C++ is what makes it
necessary to write '0' for NULL, instead of the more traditional
'(void*)0'.

Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.