This is the mail archive of the
mailing list for the GCC project.
Re: Criteria for a warning to be in -Wall? (was: Re: a warning to implement)
- From: Joe Buck <jbuck at synopsys dot COM>
- To: tim at hollebeek dot com
- Cc: gdr at codesourcery dot com (Gabriel Dos Reis),jbuck at synopsys dot COM (Joe Buck), dewar at gnat dot com (Robert Dewar),aoliva at redhat dot com, gcc at gcc dot gnu dot org, phil at jaj dot com
- Date: Wed, 6 Feb 2002 12:08:40 -0800 (PST)
- Subject: Re: Criteria for a warning to be in -Wall? (was: Re: a warning to implement)
> 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.
Many projects and development teams, both free and non-free, require
clean compiles with -Wall. What this means is that if we put an option
in -Wall, we are in a sense setting policy, the policy being that we
are asserting rather strongly that "you shouldn't do that".