From: Mike Stump <mrs AT windriver DOT com>
Date: Wed, 19 Jul 2000 14:38:04 -0700 (PDT)
Message-Id: <200007192138.OAA01286@kankakee.wrs.com>
To: eliz AT is DOT elta DOT co DOT il, martin AT loewis DOT home DOT cs DOT tu-berlin DOT de
Subject: Re: GCC headers and DJGPP port
Cc: djgpp-workers AT delorie DOT com, gcc AT gcc DOT gnu DOT org, lauras AT softhome DOT net
Reply-To: djgpp-workers AT delorie DOT com

> Date: Wed, 19 Jul 2000 14:26:25 -0400 (EDT)
> From: Eli Zaretskii <eliz AT delorie DOT com>
> To: martin AT loewis DOT home DOT cs DOT tu-berlin DOT de

> Seriously, though: the conclusion was that we didn't like the
> redefinition of NULL in C++ headers (see my other message for the
> problems this causes).  But we couldn't understand why does the C++
> compiler redefines NULL in its headers, so we couldn't find a
> solution that would satisfy us all and avoid breaking the C++
> compiler at the same time.  Perhaps you could help.

Sure, change all definitions of NULL to more closely match gcc's
notion of null, and you're done.  Sprinkle in #undef NULL if you get
redefinition errors.