diff options
| author | Dimitri van Heesch <dimitri@stack.nl> | 2014-03-15 15:50:07 (GMT) |
|---|---|---|
| committer | Dimitri van Heesch <dimitri@stack.nl> | 2014-03-15 15:50:07 (GMT) |
| commit | 941eea998d6b9608b8fc586069ef90e805d771f5 (patch) | |
| tree | 84b206b6d9fdcb807f7b4dade976c68035b34ed9 /doc/docblocks.doc | |
| parent | c1e25238950492e7f8a5c996e3d3ad41b9b023b0 (diff) | |
| download | Doxygen-941eea998d6b9608b8fc586069ef90e805d771f5.zip Doxygen-941eea998d6b9608b8fc586069ef90e805d771f5.tar.gz Doxygen-941eea998d6b9608b8fc586069ef90e805d771f5.tar.bz2 | |
Some restructuring and some compiler warning fixes
Diffstat (limited to 'doc/docblocks.doc')
| -rw-r--r-- | doc/docblocks.doc | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/docblocks.doc b/doc/docblocks.doc index 2cfff9a..6ef6bf0 100644 --- a/doc/docblocks.doc +++ b/doc/docblocks.doc @@ -460,10 +460,10 @@ settings where overruled. When using doxygen for Fortran code you should set \ref cfg_optimize_for_fortran "OPTIMIZE_FOR_FORTRAN" to \c YES. -The parser tries to guess wheter the source code is fixed format Fortran or -free format Fortran code. This is not always correct, in the later case +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 setteing `EXTENSION_MAPPING = f=FortranFixed f90=FortranFree` files with +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. |