So can the existing set of warnings that -Weffc++ enables be broken
up into fine grained warnings quite easily?
Has it already been done?
On 13 Oct 2005, at 11:44 AM, Mike Stump wrote:
On Oct 13, 2005, at 8:57 AM, Thomas Costa wrote:
I didn't want this totally tied to -Weffc++ unless
On 13 Oct 2005, at 7:41 AM, Benjamin Kosnik wrote:
yeah, if it were in one of those books it could be added to the -
weff-c+
+ option. It doesn't seem sensible to add a different option for an
alternative (set of?) coding rule(s).
FYI this is item 13 in MEC++.
It is on just about any d
o the 3.4.x and/or 4.x C++ front end that
I could help with the task?
From: Thomas Costa <[EMAIL PROTECTED]>
Date: 10 October 2005 3:34:46 PM PDT
To: [EMAIL PROTECTED]
Subject: Warning on C++ catch by value on non primitive types
Is there any way to get gcc/g++ to warn on C++ code t
