http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16168
--- Comment #8 from o...@ben-kiki.org --- Well... it does provide some really useful stuff. I think it is reasonable to expect that as long as -Weffc++ is in the compiler, it should make sense, and this specific behavior doesn't. If it has other flaws, well then, they'd also need to be fixed. One could argue that having -Weffc++ is the wrong approach in the 1st place, and what we really need is a "standard" lint++, blessed by the masters-of-C++ (assuming we can agree on who they are ;-). But that's another discussion... On Fri, Jan 10, 2014 at 5:59 PM, redi at gcc dot gnu.org < gcc-bugzi...@gcc.gnu.org> wrote: > http://gcc.gnu.org/bugzilla/show_bug.cgi?id=16168 > > --- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> --- > (In reply to Oren Ben-Kiki from comment #6) > > This still occurs in 4.8.2, and is an extremely annoying issue; it makes > > -Weffc++ very difficult to apply to a code base. > > So don't use -Weffc++ then. It's flawed in a number of ways. > > -- > You are receiving this mail because: > You are on the CC list for the bug. >
