ESTEL:ESTEL-3D code formatting guidelines

= You really have to follow these rules =


 * Comment your code!!! A lot. In English. An in a way that is understandable to those who have not written the code.
 * keep to the 72 character line limit of Fortran77 but use the other rules of Fortran90 free form. This is because some compilers seem to still have problem with longer lines. All horizontal lines in the templates are 72 characters long.* there is no need to write version numbers in the files
 * Do not use tabulation marks in the files. Tabulations are not part of Fortran90

= Important rules = Because we now use subversion to store the sources of ESTEL-3D, there are a set of rules to (try to :-) follow:* there is no need to write dates in the files. Ideally, the only date should be a lost of years at the top of each file for the EDF copyright statement.
 * try to avoid writing names and email addresses in the files unless really necessary

The above rules are there for a reason: this type of information will be obsolete very soon. Furthermore, it is very easy to find:
 * the author of a particular line in the file foo.f90, use
 * the history (as in dates, revision numbers, authors, comments) for the file foo.f90, use

= Formatting guidelines = As other people will read your code, please try to also do the following: integer, intent(in)          :: var1 ! This integer only comes in integer, intent (inout)      :: var2 ! This one comes in an out double precision, intent(out) :: var3 ! this real only goes out sub1( arg1,      &      arg2,       &      long_arg_3, &      arg4 )
 * Try to align code and comments so that it is easier to read, for instance:
 * Align arguments and continuation markers if possible: