This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]
Other format:	[Raw text]

Re: Warning on C++ catch by value on non primitive types

From: Mike Stump <mrs at apple dot com>
To: Thomas Costa <tcosta at ovro dot caltech dot edu>
Cc: Benjamin Kosnik <bkoz at redhat dot com>, gcc at gcc dot gnu dot org
Date: Thu, 13 Oct 2005 12:04:52 -0700
Subject: Re: Warning on C++ catch by value on non primitive types
References: <20051013094122.21c36d3a.bkoz@redhat.com> <01A7E769-CA3B-4994-955B-69387D2B7E07@ovro.caltech.edu> <69F86A70-9D18-422E-A05F-8A4DB1E71EFB@apple.com> <FE8ADC40-DD3D-4C69-9C06-57BE32BDD48E@ovro.caltech.edu>

On Oct 13, 2005, at 11:46 AM, Thomas Costa wrote:

So can the existing set of warnings that -Weffc++ enables be broken up into fine grained warnings quite easily?

Yes. M-x grep warn_ecpp in gcc/cp/*, then replace:

warning (0,

with

warning (OPT_Weffc_12,

and then arrange for an -Weffc_12 flag (or whatever name you like). If his new book removes one you don't like, just whack it instead. We can default ones that go against sane C++ to off, that way, we can restore the utility of the -Weffc++ flag.

Has it already been done?

No.

Sound good?

References:
- Re: Warning on C++ catch by value on non primitive types
  - From: Benjamin Kosnik
- Re: Warning on C++ catch by value on non primitive types
  - From: Thomas Costa
- Re: Warning on C++ catch by value on non primitive types
  - From: Mike Stump
- Re: Warning on C++ catch by value on non primitive types
  - From: Thomas Costa

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]