How to audit the code base to find code that is no longer used / not required?

Question

I work with a code base that has been in place for 10 years. The code has undergone numerous additions, changes, releases and refactoring without removing any code or modules that are no longer required. As a result, the code base is littered with unnecessary code.

Ask one of you to come up with a comprehensive technique or product to test your code base to find redundant unused code.

Answer 1

Assuming one way could be to run a full suite of tests and use the code coverage tool to find out which code is not executing.

PHP, http://www.google.ca/search?hl=en&q=php+code+coverage+tools 300 000 , PHP

Answer 2

, , , , , . , .

, , . , , .

Answer 3

, . get_declared_classes(), , , .

, , . , .

: http://nz.php.net/oop5.reflection

, : http://en.wikipedia.org/wiki/Connectivity_(graph_theory)

Answer 4

, /, . - Project Analyzer Visual Basic, . , .

, , - , . , , . UML/ , .

, , . , .

Answer 5

.

, , , - if- (), , .

, . , , , , , - , .

, , .

edit: , PHP. XDebug ( php), WinCachegrind (KCacheGrind , linux), , - XDebug.

Answer 6

For Java code, Bill Pugh, father of Findbugs, presented some interesting ideas for finding dead code using lightweight tools (and, of course, great ideas for static analysis) in a recent presentation on JavaOne