Content deleted Content added
→Example: exception-raising dead code cannot be removed without potentially changing the output |
→Analysis: added a paragraph about Visual Studio and Eclipse's ability to find dead code |
||
Line 25:
In large programming projects, it is sometimes difficult to recognize and eliminate dead code, particularly when entire modules become dead. Test scaffolding can make it appear that the code is still live, and at times, contract language can require delivery of the code even when the code is no longer relevant.<ref>[[Douglas W. Jones]] [http://catless.com/Risks/8.19.html#subj2 Dead Code Maintenance, Risks 8.19 (Feb. 1, 1989)]</ref>
Some [[Integrated development environment|IDE]]s (such as Visual Studio 2010 <ref>Habib Heydarian, Microsoft Corp.[http://blogs.msdn.com/b/habibh/archive/2009/07/31/discover-dead-code-in-your-application-using-code-analysis.aspx]</ref> and Eclipse Galileo <ref>Eclipse Developer Guide[http://help.eclipse.org/galileo/index.jsp?topic=/org.eclipse.jdt.doc.isv/guide/jdt_api_compile.htm]</ref>) have the ability to locate dead code during the compiling stage.
==See also==
| |||