Archive
Code Reliability
-
The code contains too many paragraph labels not followed by a dot
As much as possible, developers should always terminate paragraph labels with a dot.
-
The code contains too many dangerous usage patterns in file management
Avoid dangerous file usage patterns. File management contains dangerous usage patterns.
-
The code contains paragraphs having the same name
Paragraphs having the same name is ambigous, and should be strongly avoided.
-
The code contains too many bad area A usages
In a cobol file, area A (the first four columns) are reserved for divions, sections names, paragraph names and level 01 data declaration.
-
Avoid ‘if/else if’ & cases statements having the same condition
A chain of if/else if statements is evaluated from top to bottom. At most, only one branch will be executed: the first one with…
-
Avoid dead code
Dead code are instructions that can never be reached. Obvious dead code are instructions that follow unconditional jumps in the same statement block. Dead…
-
Avoid ‘if … else if’ constructs with missing final ‘else’ clauses
This rule applies whenever an if statement is followed by one or more else if statements; the final else if should be followed by…
-
The code contains one or more “with” instructions
The with statement in javascript inserts an object at the front scope chain, so any property/variable references will first try to be resolved against…
-
The code contains at least one class defining a destructor
For several reasons detailed in references, using finalizers is not recommended.
-
The code contains too many switch cases with missing ending breaks
Ending switch branches with ‘breaks’ helps the code be more consistent, functional, and easier to debug. This allows developers in different teams navigate the…