This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: should we use -Werror? (& sample patch to do it)
- To: "Kaveh R. Ghazi" <ghazi at caip dot rutgers dot edu>
- Subject: Re: RFC: should we use -Werror? (& sample patch to do it)
- From: Fergus Henderson <fjh at cs dot mu dot oz dot au>
- Date: Thu, 27 Sep 2001 09:51:56 +1000
- Cc: gcc at gcc dot gnu dot org
- References: <200109051909.PAA24754@caip.rutgers.edu>
On 05-Sep-2001, Kaveh R. Ghazi <ghazi@caip.rutgers.edu> wrote:
> Separately, perhaps we want something like __extension__ applied to
> regular warnings too. E.g. how about a __nowarn__ keyword that
> temporarily does "inhibit_warnings = 1" for the statement in question?
Yes, please. I've been wanting that for years.
The counter-argument is that inhibiting all warnings for a whole statement
or a whole expression is dangerous, because it might inhibit warnings that
indicate real problems. However, what I end up doing to work-around the
absence of __nowarn__ is inhibiting certain categories of warnings for my
whole application, simply because one header file contains an occurrence
of code which triggers such a warning and for which the warning can't
easily be supressed.
--
Fergus Henderson <fjh@cs.mu.oz.au> | "I have always known that the pursuit
The University of Melbourne | of excellence is a lethal habit"
WWW: <http://www.cs.mu.oz.au/~fjh> | -- the last words of T. S. Garp.