Permalink
Browse files

Bug 625601 - FORTRAN: recognition free versus fixed formatted code

Correction in documentation based on comment by dnm on June 19 2014
  • Loading branch information...
albert-github committed Jun 19, 2014
1 parent 21178ab commit 476d79d31a0534c3d7d07001c47c1212a73d10a5
Showing with 2 additions and 2 deletions.
  1. +2 −2 doc/docblocks.doc
@@ -464,8 +464,8 @@ The parser tries to guess if the source code is fixed format Fortran or
free format Fortran code. This may not always be correct. If not
one should use \ref cfg_extension_mapping "EXTENSION_MAPPING" to correct this.
By setting `EXTENSION_MAPPING = f=FortranFixed f90=FortranFree` files with
extension \c f90 are interpreted as fixed format Fortran code and files with
extension \c f are interpreted as free format Fortran code.
extension \c f are interpreted as fixed format Fortran code and files with
extension \c f90 are interpreted as free format Fortran code.
For Fortran "!>" or "!<" starts a comment and "!!" or "!>" can be used to
continue an one line comment into a multi-line comment.

0 comments on commit 476d79d

Please sign in to comment.