Page History

...

1. Be wary when using and placement of statements such as break, continue, and return, as they're indicators that segments of code are at risk of being unreachable; as stated by "Case-Based Reasoning Research and Development: 24th International Conference".  
   1. Use Structured Programming to help better the design of code therefore reducing the unnecessary use of break and continue; 
      
      
2. Modularize code as much as possible rather than combining methods/methods/classes/etc. into one.
   1. "Facilitating Unreachable Code Diagnosis and Debugging"[Chou, Chang, Kuo 2011] explains why this is an issue in their paper; they state ...
      "In order to support design reuse, a circuit may have multiple modes and configurations so that it can be used in different applications. When verifying a specific configuration, a substantial amount of unused code may be discovered because the code may be written for other modes."
      
      
      
3. Avoiding putting in dead code, such as empty function or placeholders, an issue stated by "Facilitating Unreachable Code Diagnosis and Debugging" . If dead code is temporarily used as place holder, remove before release of app.

...

Bibliography