This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: PATCH: Wno-warning-directives [WasRe: cpplib: Start moving ...]
- From: Stan Shebs <shebs at apple dot com>
- To: Mark Mitchell <mark at codesourcery dot com>
- Cc: Geoff Keating <geoffk at geoffk dot org>, Devang Patel <dpatel at apple dot com>, "gcc-patches at gcc dot gnu dot org" <gcc-patches at gcc dot gnu dot org>
- Date: Tue, 13 Aug 2002 12:33:57 -0700
- Subject: Re: PATCH: Wno-warning-directives [WasRe: cpplib: Start moving ...]
- References: <53310000.1029265841@warlock.codesourcery.com>
Mark Mitchell wrote:
Apple GCC has the features, but we offer them for FSF GCC in the
belief that if they're useful at Apple, they're quite possibly
useful elsewhere.
But so far the consensus here seems to be that people don't see this
new switch as useful elsewhere. So, that's the kind of thing that's
perfect for Apple GCC -- something useful to Apple but not elsewhere.
It seems so. I wanted to be sure that people understand the
rationale, and not dismiss as "one of those weird Apple things".
Amusingly, one of the other warnings we added turns out to be
identical to the recently-added -Wendif-labels, and I'm glad
not to have to argue about the value of that one!
In response to your philosophical point, while limiting the
functionality of the compiler saves a little work in the short
term, it's not clever in the long term, because you lose all
your customers.
This is a reduction-to-absurdity argument.
Nobody is suggesting we not add functionality to the compiler; we're
all working on that all the time. The question is what functionality.
Well, you did complain about adding switches in general. I think
it's the wrong thing to complain about, because users generally
consider the wide selection of switchable warnings to be one of
GCC's main strengths. Have you not ever heard that from users
yourself?
Stan