Date:	Thu, 20 Jul 2000 10:37:16 -0400
Message-Id:	<200007201437.KAA29757@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	djgpp-workers AT delorie DOT com
CC:	gcc AT gcc DOT gnu DOT org
In-reply-to:	<200007201205.OAA15361@loewis.home.cs.tu-berlin.de>
	(martin AT loewis DOT home DOT cs DOT tu-berlin DOT de)
Subject:	Re: GCC headers and DJGPP port
References:	<200007180918 DOT FAA06988 AT indy DOT delorie DOT com> <200007181913 DOT VAA01170 AT loewis DOT home DOT cs DOT tu-berlin DOT de> <200007191826 DOT OAA08693 AT indy DOT delorie DOT com> <200007200729 DOT JAA01060 AT loewis DOT home DOT cs DOT tu-berlin DOT de> <200007201024 DOT GAA09536 AT indy DOT delorie DOT com> <200007201205 DOT OAA15361 AT loewis DOT home DOT cs DOT tu-berlin DOT de>
Reply-To:	djgpp-workers AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp-workers AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

> I don't know what your copy of stdio.h looks like, however, it
> should certainly test whether NULL is defined before defining it.

It doesn't.  It shouldn't have to.  ANSI says that stdio.h provides
NULL.  I have a philosophical problem with anyone saying "it should
certainly test it" because it means that, at the whim of the gcc team,
we'd need to add yet another test to our standard headers because yet
another symbol was absconded by the gcc headers.  Where does it end?
Do we have to wrap every single #define in all the system headers?
Will we have to wrap the function prototypes also?

Of course, a working fixincludes might circumvent the technical
problems.

- Raw text -