From: Mike Stump <mrs AT windriver DOT com>
Date: Thu, 20 Jul 2000 13:34:52 -0700 (PDT)
Message-Id: <200007202034.NAA01736@kankakee.wrs.com>
To: eliz AT is DOT elta DOT co DOT il
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,
        martin AT loewis DOT home DOT cs DOT tu-berlin DOT de
Reply-To: djgpp-workers AT delorie DOT com

> Date: Thu, 20 Jul 2000 02:42:48 -0400 (EDT)
> From: Eli Zaretskii <eliz AT delorie DOT com>
> To: mrs AT windriver DOT com

> > From: Mike Stump <mrs AT windriver DOT com>
> > Date: Wed, 19 Jul 2000 14:38:04 -0700 (PDT)
> > 
> I'm not sure what GCC's notion of NULL are you talking about.

gcc only has one definition of NULL.  After you read it, it was my
hope you would understand it.  If you don't, you might trye
comp.lang.c.

> We cannot use __null in C headers unconditionally,

Ok, I already know that.  You must misunderstand my point if you think
I said that.

> Use of __null conditioned on __cplusplus is questionable,

At this point, I will just say trust me, do it.  You can either ignore
me, or listen to me, your choice.

> since libc.a is not compiled with that definition of NULL.  Am I
> missing something?

Yes.

> > Sprinkle in #undef NULL if you get redefinition errors.
>  
> We did use #undef to solve the immediate problem, but it looked like a
> brute-force and potentially dangerous (for C++ programs) solution.  I
> wonder if there's a better one.

No.