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

[Geoff Keating <geoffk at geoffk dot org>]

> Date: Tue, 13 Aug 2002 11:31:12 -0700
> From: Stan Shebs <shebs@apple.com>

> Hindsight is always 20/20, eh?  What I believe happened is that there
> are some groups within Apple that use #warning a lot; they may even
> have it as part of their coding standard.  I just grepped through
> public headers in OS X, and there are several hundred of these; private
> headers have even more.  We have other groups that require building
> with -Werror before their code can go into the system.  This works
> fine until the -Werror folks have to add a feature that involves an
> API with the #warnings.
> 
> Certainly if there were a god of OS X that could come down and smite
> engineers until they agreed on everything, this would not be an issue.
> But there is literally no way to get this kind of agreement.  Since
> there are no other system vendors using GCC on Apple's scale (Cisco
> is probably the closest), it's not surprising that this flaw in
> #warning seemed unimportant.

Cisco does have similar problems.  They don't, however, use -Werror;
they use grep (or actually something more complicated, I think) on the
compiler's output, which is another possible solution to your problem.

-- 
- Geoffrey Keating <geoffk@geoffk.org> <geoffk@redhat.com>