Your approach appears more throrough than what I've been attempting. My hypothesis so far is that a fair amount of information can be obtained straight from the binaries in the program/ directory without analyzing the source code.
One thing I've learned is that the the ELF symbol tables and relocation tables do provide a lot of information, including revealing some of the symbols that are used internally within the binaries. However, there is a lot of room for source-based analysis like your tool or the commercial C++ lint tools. Matt --- Caolan McNamara <[EMAIL PROTECTED]> wrote: > > FWIW here's the approach I took to find unused code, scrape the > compiler output to get what functions were defined and which were > called, detect virtual methods and ignore those > http://www.skynet.ie/~caolan/Packages/callcatcher.html > > > C. __________________________________ Do you Yahoo!? Yahoo! Mail - You care about security. So do we. http://promotions.yahoo.com/new_mail --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
