Changes between Version 4 and Version 5 of FpCodingStandard


Ignore:
Timestamp:
Feb 13, 2015, 6:58:11 PM (4 years ago)
Author:
pesei
Comment:

Use INTENT?

Legend:

Unmodified
Added
Removed
Modified
  • FpCodingStandard

    v4 v5  
    1010  4. Use indentations for loops, `if`-statements, etc. From start till end of loop, all code lines should be indented by 2 spaces; nested loops should have multiple indentations so that the looping level is always clear. Because of automatic transcription to F90 standards, a lot of this has been lost and we should try to reintroduce this whereever it has been lost. Indenting by whitespace only, not tab characters (check your editor settings!).
    1111
    12   5. Variables that are passed between subroutines should be marked in the subroutine as input (`i)`, output (`o`) or both (`i/o`) when values are changed both in the subroutine and in other routines. This should be done just below the subroutine statement. Again, this has become a mess because of the automatic transcription. We will try to make it systematic again.
     12  5. Variables that are passed between subroutines should be marked in the subroutine as input (`i)`, output (`o`) or both (`i/o`) when values are changed both in the subroutine and in other routines. This should be done just below the subroutine statement. Again, this has become a mess because of the automatic transcription. We will try to make it systematic again.
     13 
     14  ''Is it also acceptable if an INTENT keyword is present in the declaration section?''
    1315
    1416  6. If you make changes in a subroutine, explain them in the header: Who? Why? What? When?