GCC headers and DJGPP port

[Eli Zaretskii]

> Date: Tue, 18 Jul 2000 21:13:22 +0200
> From: "Martin v. Loewis" <martin@loewis.home.cs.tu-berlin.de>
> 
> > Anyway, one reason that __null might cause trouble is that it breaks
> > previous versions of the library which were compiled with different
> > definition of NULL.  I think we've been discussing that on the DJGPP
> > developers list to death.
> 
> And did these discussions come to a conclusion, or did everybody die
> before that?

You are talking to a few survivors ;-).

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.