Mail Archives: djgpp-workers/2000/05/17/09:48:37
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
- Raw text -