This is the mail archive of the
mailing list for the GCC project.
Criteria for a warning to be in -Wall? (was: Re: a warning to implement)
- From: Tim Hollebeek <tim at hollebeek dot com>
- To: Gabriel Dos Reis <gdr at codesourcery dot com>
- Cc: Joe Buck <jbuck at synopsys dot com>, Robert Dewar <dewar at gnat dot com>, aoliva at redhat dot com, gcc at gcc dot gnu dot org, phil at jaj dot com
- Date: Wed, 6 Feb 2002 14:49:01 -0500
- Subject: Criteria for a warning to be in -Wall? (was: Re: a warning to implement)
- References: <200202061847.KAA04566@atrus.synopsys.com> <firstname.lastname@example.org>
- Reply-to: tim at hollebeek dot com
> As an aside, I'm a bit surprised to see that far more misleading
> constructs should be warned about by GCC, but the corresponding flags
> are not turned on by -Wall and yet nobody is arguing so strongly about
> having them in -Wall. An example is -Wnested-externs.
Let's discuss what the conditions should be for a warning to be in
-Wall, and then document it. If that ends up meaning -Wnested-externs
should be added, so be it.