User Tools

Site Tools


developers:coding_rules

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revisionBoth sides next revision
developers:coding_rules [2021/08/31 16:21] – [4. File format] Jean-Michel Beukendevelopers:coding_rules [2021/08/31 20:28] – [4. Constructs for flow control] Xavier Gonze
Line 401: Line 401:
 In all other cases, specify an 'intent(inout)' and detail (with comments) the status for each field. In all other cases, specify an 'intent(inout)' and detail (with comments) the status for each field.
  
-====== 4. Constructs for flow control ======+====== 5. Constructs for flow control ======
  
-4.a. Do not use numeral labels. These can be avoided through the use of the construct+5.a. Do not use numeral labels. These can be avoided through the use of the construct
  
    DO ...    DO ...
Line 420: Line 420:
 A character string can be explicitly declared, then initialized, if it is to be used more than once. (enforced) A character string can be explicitly declared, then initialized, if it is to be used more than once. (enforced)
  
-4.b. Literal labels or comment lines must be used for each construct that is longer than one page of a screen (about 20 lines), both at the beginning and at the end of the construct. (enforced)+5.b. Literal labels or comment lines must be used for each construct that is longer than one page of a screen (about 20 lines), both at the beginning and at the end of the construct. (enforced)
  
 ====== 5. Use of arrays ====== ====== 5. Use of arrays ======
developers/coding_rules.txt · Last modified: 2021/08/31 20:35 by Xavier Gonze