Changes between Version 33 and Version 34 of HowTo/FortranStandards

Timestamp:

2013-06-25T13:29:38+02:00 (11 years ago)

Author:

luyssaert

Comment:

--

HowTo/FortranStandards

@@ -137 +137 @@
 
 NOTE: The emacs indent function works well for this, since it indents with spaces (even if you use the tab key).
+
+(6) '''Document units:''' Use comment lines to document units and unit conversions
+
+(7) '''Document your thinking:''' Document your thinking rather than simply the describing the fortran code in 
+
 ----
 
@@ -176 +181 @@
 '''IF''' bavard '''>=''' 3 then input parameters to major subroutines are reported 
 [[BR]] 
+
+(2) '''personal debug flags:'''
 
 (2) '''Don't forget the ELSE:''' If you are using an IF...ELSEIF....ENDIF loop, always make sure you include an ELSE statement at the end to catch any situation not covered in the other cases.  This should be done even if the ELSE statement doesn't do anything, just so that other people know that nothing needs to be done in some cases.  Too many bugs are found because an IF statement is not triggered due to something the programmer didn't think of.  This is especially problematic when the  programmer thinks to him/herself, "This value will always be in this range, so I don't have to consider other possibilities"...and then one day things change.