Date: Wed, 8 Mar 2000 15:10:18 -0500
Message-Id: <200003082010.PAA23972@envy.delorie.com>
From: DJ Delorie <dj AT delorie DOT com>
To: eliz AT is DOT elta DOT co DOT il
CC: broeker AT physik DOT rwth-aachen DOT de, djgpp-workers AT delorie DOT com
In-reply-to: <Pine.SUN.3.91.1000308155050.8110E-100000@is> (message from Eli
	Zaretskii on Wed, 8 Mar 2000 15:53:46 +0200 (IST))
Subject: Re: iso646.h and some questions
References:  <Pine DOT SUN DOT 3 DOT 91 DOT 1000308155050 DOT 8110E-100000 AT is>
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


> > 	#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?

What's wrong with the solution we've been using?

	#include <sys/djtypes.h>
	__DJ_va_list
	#undef __DJ_va_list
	#define __DJ_va_list

As far as NULL itself is concerned, we've been through this before.
DJGPP's headers will replace g++'s NULL with a zero if they can.