Changes between Version 27 and Version 28 of HowTo/FortranStandards


Ignore:
Timestamp:
2013-05-21T09:25:00+02:00 (12 years ago)
Author:
mmcgrath
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • HowTo/FortranStandards

    v27 v28  
    3838The reason is that subroutine arguments are not strictly checked, so when one is hunting 
    3939for bugs, it's nice to be able to quickly check that all the arguments are in the right place. 
     40> MJM: Thanks to Lionel Guez, I've run some additional tests.  This is not standard behavior in gfortran, so the times when this occured must have been a special circumstance and not the norm.  Therefore, this rule is probably not required. 
     41 
    4042---- 
    4143 
     
    102104}}} 
    103105 
     106> MJM: Lionel has suggested to label the loops instead.  This would also be fine. 
     107 
    104108 
    105109[[BR]]  
     
    164168}}} 
    165169 
     170> MJM: if nothing is done in the ELSE, it could have something written in a comment instead.  As long as it is clear that the programmer has thought of the possibility that the loop is not triggered, it's fine by me. 
     171  
     172 
    166173[[BR]]  
    167174