Yang Zhang <yanghatespam@xxxxxxxxx> writes: > What I really intended to ask: is there any hope of seeing GCC not > issue warnings for expansions of macros that were defined in a C > standard library, such that users don't need to read through and > re-define these C standard library macros? I think that would be a useful feature. Unfortunately, it would be not very easy to implement. But certainly I would encourage people to write patches for this. The approach more traditionally used by gcc is to fix the offending constructs with the fixincludes scripts, to rewrite them such that they do not cause warnings. That can be fairly difficult for avoiding C++ warnings, though. Ian
