Re: [GD-General] C++ analyzers?

[Parveen K. <pk...@sf...>]

Brian Hook wrote:
> One of my bitches about software development are that the tools suck.
> Many things that can and should be automated simply aren't.  Tools like
> Emacs and make provide a lot of helpers when you have to do this manual
> stuff, but they don't actually solve problems that are language specific
> (since those tools aren't language specific).
> 
[snip]

If your using emacs, etags might be a little more helpful than grep in certain 
cases.
http://www.gnu.org/manual/emacs-21.2/html_chapter/emacs_26.html#SEC334

Or ebrowse, which is specifically for C++, but I haven't ever used it.
http://www-es.fernuni-hagen.de/cgi-bin/info2html?(ebrowse)Top

If your using emacs, seems you might be using gcc as well.  It's always a good 
idea to turn on all warnings (and most people do) with -Wall.

There are a bunch of compilation switches that aren't covered by -Wall that I 
like to use:
-Weffc++ -Wold-style-cast -pedantic -Wunreachable-code -ansi

-Weffc++ catches a few of items (but not nearly enough) from Scott Meyer's 
Effective C++, which is a pretty cool concept.

I've never used gcov.
http://gcc.gnu.org/onlinedocs/gcc-3.1/gcc/Gcov.html#Gcov
Does anyone have any experience with it?  Seems like it might be able to find 
some of that "vestigial cruft".
I guess gprof, or any other good profiler, can be used to get the same effect.

Don't know how useful these primarily *nix tools will be since a lot of 
developers are probably sitting in Win32 land.

Parveen