PATCH: Wno-warning-directives [WasRe: cpplib: Start moving ...]

[Devang Patel]

On Monday, August 12, 2002, at 06:35  PM, Richard Henderson wrote:

> On Mon, Aug 12, 2002 at 05:31:56PM -0700, Stan Shebs wrote:
>> ... you're screwed if an evil header developer adds something like
>>
>>    #warning "Revisit this typedef after Jaguar ships."
>
> Well, yes, you are screwed.  I can't help it if some of
> your developers are idiots.  All I can suggest is that
> you teach them to do otherwise.  And then edit your local
> copy of the header to delete the warning.
>
> It's similar to the problem of glibc using gcc extensions
> without __extension__, which generates -pedantic warnings.
> (Except that Uli fixes these when found.  ;-)
>

In that case, is it appropriate to argue that gcc does
not need "-Wno-system-headers" flag ?

-Devang

In theory, there is no difference between theory and practice,
but in practice, there is.  -Unknown