There are many different programming styles, but here are some general guidelines that are fairly non-controversial.
To ensure portability, use only standard FORTRAN 77. The only exception we have allowed in this tutorial is to use lower case letters.
The overall program structure should be modular. Each subprogram should solve a well-defined task. Many people prefer to write each subprogram in a separate file.
Write legible code, but also add comments in the source explaining what is happening! It is especially important to have a good header for each subprogram that explains each input/output argument and what the subprogram does.
Always use proper indentation for loops, and for if blocks, as demonstrated in this tutorial.
Always declare all variables. Implicit type declaration is bad! Try to stick to a maximum of 6 characters for variable names, or at the very least make sure the first 6 characters are unique.
Never let functions have "side effects", i.e. do not change the value of the input parameters. Use subroutines in such cases.
In the declarations, separate parameters, common blocks, and local variables.
Minimize the use of common blocks.
Minimize the use of goto. Unfortunately it is necessary to use goto in some loops since while is not standard Fortran.
In many cases it is best to declare all large arrays in the main program and then pass them as arguments to the various subroutines. This way all the space allocation is done in one place. Remember to pass the leading dimensions. Avoid unnecessary "reshaping" of matrices.
When you have a double loop accessing a two-dimensional array, it is usually best to have the first (row) index in the innermost loop. This is because of the storage scheme in Fortran.
When you have if-then-elseif statements with multiple conditions, try to place the most likely conditions first.
Copyright © 1995-7 by Stanford University. All rights reserved.
[ Index ]