Message-ID: <392291D2.746E115D@softhome.net>
Date: Wed, 17 May 2000 15:34:26 +0300
From: Laurynas Biveinis <lauras AT softhome DOT net>
X-Mailer: Mozilla 4.72 [en] (Win98; U)
X-Accept-Language: en
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com, Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
Subject: Re: Minor GCC & DJGPP header problem
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1000517101928 DOT 4709F-100000 AT is>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Eli Zaretskii wrote:
> Note that this is becoming ridiculous: do we really need to #undef
> each macro before defining it, just to pacify GCC's invasive
> practices?  These are _system_ headers, for crying out loud!  A
> library implementation should be free to define these macros in any
> way it sees fit without fear.

I take your point and IMHO you're right. I see that I've looked for
a wrong fix.

> Why does GCC need to define offsetof, anyway?  And why can't it
> include the system header where it should be defined according to
> ANSI, *before* using its own definition?  If it did that, the ifndef
> thing inside GCC's header would do the Right Thing.

It includes <stdio.h> and then conditionally defines NULL and offsetof.
I'll make a patch for GCC which will #include <stddef.h> (if present) too.
This should fix it.

Laurynas Biveinis