This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: GCC headers and DJGPP port
- To: martin at loewis dot home dot cs dot tu-berlin dot de
- Subject: Re: GCC headers and DJGPP port
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Wed, 19 Jul 2000 14:26:25 -0400 (EDT)
- CC: lauras at softhome dot net, mrs at windriver dot com, gcc at gcc dot gnu dot org, djgpp-workers at delorie dot com
- References: <200007180918.FAA06988@indy.delorie.com> <200007181913.VAA01170@loewis.home.cs.tu-berlin.de>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> 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.