Ask Slashdot: What Tools To Clean Up a Large C/C++ Project?

Posted by timothy on Thursday February 5, 2015 @06:10AM from the windex-is-a-start dept.

An anonymous reader writes I find myself in the uncomfortable position of having to clean up a relatively large C/C++ project. We are talking ~200 files, 11MB of source code, 220K lines of code. A superficial glance shows that there are a lot of functions that seem to be doing the same things, a lot of 'unused' stuff, and a lot of inconsistency between what is declared in .h files and what is implemented in the corresponding .cpp files. Are there any tools that will help me catalog this mess and make it easier for me to locate/erase unused things, clean up .h files, and find functions with similar names?

2 of 233 comments (clear)

Min score:

Reason:

Sort:

Static analysis tools... by underqualified · 2015-02-05 06:13 · Score: 5, Informative

If you're company is willing to pay for it, you can get something like Coverity. On the free(as in beer) side there is CppCheck and clang.
clang static code analysis by Anonymous Coward · 2015-02-05 06:15 · Score: 5, Informative

scan-build and scan-view from clang++ will show you what is being used and what isn't as far as static code analysis goes.