Unreachable code (English Wikipedia)

Analysis of information sources in references of the Wikipedia article "Unreachable code" in English language version.

refsWebsite
Global rank English rank
207th place
136th place
2nd place
2nd place
11th place
8th place
low place
low place
low place
low place
low place
low place
low place
low place
low place
low place
67th place
64th place
1,564th place
1,028th place
5,060th place
4,600th place

apple.com

opensource.apple.com

avandeursen.com

cmu.edu

wiki.sei.cmu.edu

  • "MSC15-C. Do not depend on undefined behavior". Carnegie Mellon University. 2020. Retrieved 28 September 2020. Because compilers are not obligated to generate code for undefined behavior, these behaviors are candidates for optimization.

doi.org

imperialviolet.org

ldra.com

  • Jay Thomas (24 January 2017). "Requirements Traceability Forms the Foundation for Thorough Software Testing". Retrieved 2019-06-11. The combination of requirements traceability with coverage analysis can also turn up areas of "dead code," or code that's never executed. This code can mostly be an inconvenience, but it can also be a security threat if a hacker can gain access and from there gain control. It's code that can't be traced and should therefore be eliminated.

misra.org.uk

psu.edu

citeseerx.ist.psu.edu

rtca.org

my.rtca.org

  • RTCA/DO-178C Software Considerations in Airborne Systems and Equipment Certification. RTCA, Inc. 2011. p. 112. Retrieved 2019-06-11. Dead code – Executable Object Code (or data) which exists as a result of a software development error but cannot be executed (code) or used (data) in any operational configuration of the target computer environment. It is not traceable to a system or software requirement. The following exceptions are often mistakenly categorized as dead code but are necessary for implementation of the requirements/design: embedded identifiers, defensive programming structures to improve robustness, and deactivated code such as unused library functions. [Since requirements-based review should identified such code as untraceable to functional requirements, static code analysis should identify such code as unreachable, and structural coverage analysis of requirements-based testing results should identify such code as unreachable, presence of unjustified dead code in a project should raise consideration of the effectiveness of the organization's development and verification processes.]

semanticscholar.org

api.semanticscholar.org

sun.com

java.sun.com