https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80529
--- Comment #3 from Jonathan Wakely <redi at gcc dot gnu.org> --- (In reply to Eric Gallager from comment #2) > (In reply to Jonathan Wakely from comment #1) > > IMHO warnings should not be enforcing in-house coding guidelines. Use > > clang-tidy for that. > > GCC already has several warnings added for that purpose. -Wtemplates, > -Wmultiple-inheritance, -Wvirtual-inheritance, and -Wnamespaces are all > documented as existing because: > "Some coding rules disallow > [templates|[multiple|virtual]inheritance|namespaces], and this may be used > to enforce that rule." Five wrongs don't make a right. I stand by my opinion. > And then -Weffc++ is also documented as being a set of style guidelines. The Effective C++ rules are about things that often cause bugs, not just aesthetic style. And -Weffc++ is completely broken anyway (see numerous bugs). > Also it seems odd that a GCC developer would recommend using a clang-based > tool instead of GCC when clang is a competing project designed specifically > to undermine GCC. Because I'm not childish and realise that clang-tidy is a better tool than a compiler when you want to enforce style guides.
