Date:	Wed, 8 Mar 2000 15:53:46 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
cc:	djgpp-workers AT delorie DOT com, DJ Delorie <dj AT delorie DOT com>
Subject:	Re: iso646.h and some questions
In-Reply-To:	<Pine.LNX.4.10.10003081434500.16372-100000@acp3bf>
Message-ID:	<Pine.SUN.3.91.1000308155050.8110E-100000@is>
MIME-Version:	1.0
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

On Wed, 8 Mar 2000, Hans-Bernhard Broeker wrote:

> Then, all the
> 
> 	#undef NULL
> 	#define NULL 0
> 
> sequences in the C standard headers could be replaced by
> 
> 	#include <sys/djnull.h>
> 	#ifndef NULL
> 	#define NULL _DJ_NULL
> 	#endif

I like this better.  But isn't it cleaner to have all the #ifndef stuff 
inside sys/djnull.h, instead of exposing it to the public headers?

DJ, do you agree to this solution?

> This should work for both C and C++ compiles. Or doesn't the C++ __null
> evaluate to a C-usable NULL pointer constant, if passed to an extern "C"
> function?

I never took the time to look at the C++ definition and reflect on its 
fine points.  Anyone?

- Raw text -