summaryrefslogtreecommitdiffstats
path: root/src/util.h
diff options
context:
space:
mode:
authoralbert-github <albert.tests@gmail.com>2014-03-09 17:57:12 (GMT)
committeralbert-github <albert.tests@gmail.com>2014-03-09 17:57:12 (GMT)
commit2dec1060623165057628ee678eb3580351922408 (patch)
tree24f78a22f5220010d75f86a6f6702996b7d1fb0a /src/util.h
parent8eeaae0b06fd320745f22efe176e0f19d6c8e2a6 (diff)
downloadDoxygen-2dec1060623165057628ee678eb3580351922408.zip
Doxygen-2dec1060623165057628ee678eb3580351922408.tar.gz
Doxygen-2dec1060623165057628ee678eb3580351922408.tar.bz2
Bug 625601 - FORTRAN: recognition free versus fixed formatted code
The recognition of the type (free or fixed) of Fortran code is not reliable possible. A well known possibility as used with compilers as well is to specify the type of code by means of the extension. With EXTENSION_MAPPING it is possible to select the type of Fortran code, when not explicitly set doxygen tries to guess the type of Fortran code.
Diffstat (limited to 'src/util.h')
-rw-r--r--src/util.h2
1 files changed, 2 insertions, 0 deletions
diff --git a/src/util.h b/src/util.h
index c3ecad5..5f9a873 100644
--- a/src/util.h
+++ b/src/util.h
@@ -414,6 +414,8 @@ QCString externalRef(const QCString &relPath,const QCString &ref,bool href);
int nextUtf8CharPosition(const QCString &utf8Str,int len,int startPos);
const char *writeUtf8Char(FTextStream &t,const char *s);
+enum FortranKind { FORTRAN_UNKNOWN = 0, FORTRAN_FREE, FORTRAN_FIXED};
+
/** Data associated with a HSV colored image. */
struct ColoredImgDataItem
{