diff options
| author | albert-github <albert.tests@gmail.com> | 2014-06-19 15:50:27 (GMT) |
|---|---|---|
| committer | albert-github <albert.tests@gmail.com> | 2014-06-19 15:50:27 (GMT) |
| commit | 476d79d31a0534c3d7d07001c47c1212a73d10a5 (patch) | |
| tree | 685ac9f4a2481bf3e90d16676e1e8b08d0b98854 /doc/docblocks.doc | |
| parent | 21178ab40160abf011fa084a10892b5b7821e44c (diff) | |
| download | Doxygen-476d79d31a0534c3d7d07001c47c1212a73d10a5.zip Doxygen-476d79d31a0534c3d7d07001c47c1212a73d10a5.tar.gz Doxygen-476d79d31a0534c3d7d07001c47c1212a73d10a5.tar.bz2 | |
Bug 625601 - FORTRAN: recognition free versus fixed formatted code
Correction in documentation based on comment by dnm on June 19 2014
Diffstat (limited to 'doc/docblocks.doc')
| -rw-r--r-- | doc/docblocks.doc | 4 |
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. |