From mboxrd@z Thu Jan 1 00:00:00 1970 From: Eli Zaretskii To: martin@loewis.home.cs.tu-berlin.de Cc: lauras@softhome.net, mrs@windriver.com, gcc@gcc.gnu.org, djgpp-workers@delorie.com Subject: Re: GCC headers and DJGPP port Date: Wed, 19 Jul 2000 11:26:00 -0000 Message-id: <200007191826.OAA08693@indy.delorie.com> References: <200007180918.FAA06988@indy.delorie.com> <200007181913.VAA01170@loewis.home.cs.tu-berlin.de> X-SW-Source: 2000-07/msg00584.html > Date: Tue, 18 Jul 2000 21:13:22 +0200 > From: "Martin v. Loewis" > > > 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.