Dead code: Difference between revisions

Revision as of 07:25, 7 May 2009

Revision as of 21:37, 3 June 2009

Line 3:

'''Dead code''' is a [[computer programming]] term for code in the [[source code]] of a program which is executed but whose result is never used in any other computation.<ref>[http://doi.acm.org/10.1145/349214.349233 Debray, S. K., Evans, W., Muth, R., and De Sutter, B. 2000. Compiler techniques for code compaction. ACM Trans. Program. Lang. Syst. 22, 2 (Mar. 2000), 378-415.]</ref><ref>[[Andrew Appel|Appel, A. W.]] 1998 Modern Compiler Implementation in Java. Cambridge University Press.</ref> The execution of dead code wastes computation time as its results are never used.

While the result of a dead computation may never be used the dead code may raise [[exceptions]] or affect some global state, thus removal of such code may change the output of the program and introduce unintended [[software_bugsoftware bug|bugs]]. Compiler optimizations are typically conservative in their approach to dead code removal if there is any ambiguity as to whether removal of the dead code will affect the program output.

== Example ==

Line 32:

{{reflist}}

== External links ==

* [https://dcd.dev.java.net/ Dead Code Detector (DCD) simply finds never used code in your Java/JEE applications]

* [https://dcd.dev.java.net/alternatives.html Comparisons of some Java Dead Code Detector]

{{DEFAULTSORT:Dead Code}}

[[Category:Compiler optimizations]]

[[Category:Software engineering terminology]]

[[Category:Source code]]

== External links ==

* [https://dcd.dev.java.net/ Dead Code Detector (DCD) simply finds never used code in your Java/JEE applications]

* [https://dcd.dev.java.net/alternatives.html Comparisons of some Java Dead Code Detector]