summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorDimitri van Heesch <dimitri@stack.nl>2014-06-20 18:30:57 (GMT)
committerDimitri van Heesch <dimitri@stack.nl>2014-06-20 18:30:57 (GMT)
commit1fc2a65a6cbc7ce23f13411662323f2757f5b42a (patch)
treefa2dbc6e43d84ad2c13370b35285f182c2fa73b9
parent6617df2fa4ebd93ba437ac8ecc704b6cd7a1ef6a (diff)
parent476d79d31a0534c3d7d07001c47c1212a73d10a5 (diff)
downloadDoxygen-1fc2a65a6cbc7ce23f13411662323f2757f5b42a.zip
Doxygen-1fc2a65a6cbc7ce23f13411662323f2757f5b42a.tar.gz
Doxygen-1fc2a65a6cbc7ce23f13411662323f2757f5b42a.tar.bz2
Merge pull request #185 from albert-github/feature/bug_625601
Bug 625601 - FORTRAN: recognition free versus fixed formatted code
-rw-r--r--doc/docblocks.doc4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/docblocks.doc b/doc/docblocks.doc
index 6ef6bf0..c74211c 100644
--- a/doc/docblocks.doc
+++ b/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.