summaryrefslogtreecommitdiffstats
path: root/src/fortrancode.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/fortrancode.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/fortrancode.h')
-rw-r--r--src/fortrancode.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/fortrancode.h b/src/fortrancode.h
index 8c947e9..2beea69 100644
--- a/src/fortrancode.h
+++ b/src/fortrancode.h
@@ -28,7 +28,7 @@ void parseFortranCode(CodeOutputInterface &,const char *,const QCString &,
bool ,const char *,FileDef *fd,
int startLine,int endLine,bool inlineFragment,
MemberDef *memberDef,bool showLineNumbers,Definition *searchCtx,
- bool collectRefs);
+ bool collectRefs, FortranKind codeType);
void resetFortranCodeParserState();
void codeFreeScanner();