Message-Id: <m0yqfZj-000S3EC@inti.gov.ar>
Comments: Authenticated sender is <salvador AT natacha DOT inti DOT gov DOT ar>
From: "Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>
Organization: INTI
To: DJ Delorie <dj AT delorie DOT com>, djgpp-workers AT delorie DOT com
Date: Mon, 29 Jun 1998 12:16:52 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: NULL and C++ headers
In-reply-to: <199806290507.BAA29783@delorie.com>
Precedence: bulk

DJ Delorie <dj AT delorie DOT com> wrote:

 
> Note that the alpha has the "#undef NULL" workaround (NOT A FIX) for
> the C++ NULL/__null issue.  This is temporary, to solicit feedback.
> If left in, I'd like to do something like this:

That's good.

> #ifdef NULL
> #if NULL .ne. "0"  /* don't know how yet */

I don't know how to do it too. But be careful __null is like 0 but some tricky 
comparisson here could report the reverse thing.

> #warn Your program defined NULL to something unexpected
> #warn DJGPP's stdio.h has set NULL back to what it should be

Yes perhaps you can put a warning anyways, because if the ANSI standard says 
that stdio must define it a warning is needed. 

> #endif
> #undef NULL
> #endif
> #define NULL ...

SET 
------------------------------------ 0 --------------------------------
Visit my home page: http://set-soft.home.ml.org/
or
http://www.geocities.com/SiliconValley/Vista/6552/
Salvador Eduardo Tropea (SET). (Electronics Engineer)
Alternative e-mail: set-soft AT usa DOT net set AT computer DOT org
ICQ: 2951574
Address: Curapaligue 2124, Caseros, 3 de Febrero
Buenos Aires, (1678), ARGENTINA
TE: +(541) 759 0013