Let me tell you all something. There is one wonderful thing about releasing a piece of software: You get all kinds of suggestions of tools you've never heard of. That alone is worth the effort.
How does your software relate to the gcov utlity as far as tracking unused portions of code? What about the -fprofile-arcs and -ftest-coverage gcc flags?
Do we have someone in the club who is really good with gcc and binutils? I'm ashamed to admit I had no idea about gcc's profiling flags, and there are probably more useful things I don't know about. How about a "Binutils Magic" lecture by some gcc wizard?
Now to the point: cdepend doesn't deal with if a function was called or not in effect, but only if it's *mentioned* within a portion of code. If a call to a function depends on a condition that is never met, this unused function will not be detected by cdepend, and will be detected by gcc/gcov. On the other hand, on a large project it may be very difficult to test the target project extensively enough to expose unused functions with gcc/gcov.
Both tools give their results depending on the configuration of the relevant compilation, which is a common drawback: Some function may appear unused, while being important on another architecture or environment.
So I suppose that cdepend and gcc/gcov relate to each other as complimentary tools.
Thanks for the tip.
Eli
-- Web: http://www.billauer.co.il
-------------------------------------------------------------------------- Haifa Linux Club Mailing List (http://www.haifux.org) To unsub send an empty message to [EMAIL PROTECTED]
