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

Mike Stump mrs@apple.com
Thu Oct 13 19:31:00 GMT 2005


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?



More information about the Gcc mailing list