summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authoralbert-github <albert.tests@gmail.com>2020-09-18 19:04:53 (GMT)
committerGitHub <noreply@github.com>2020-09-18 19:04:53 (GMT)
commit1206a9b9b49cdd904c1b5f003c874acd94472806 (patch)
treed3276f0365116b5c199b7e5c528ea147b701083f
parent254d1106e52f89fc69620dded9a670358818e8e6 (diff)
downloadDoxygen-1206a9b9b49cdd904c1b5f003c874acd94472806.zip
Doxygen-1206a9b9b49cdd904c1b5f003c874acd94472806.tar.gz
Doxygen-1206a9b9b49cdd904c1b5f003c874acd94472806.tar.bz2
Fortran comments with C comments inside (#8000)
When having a (stripped down) example like: ``` ! !!/*T !T*/ ``` we get a warning like: ``` .../ex11f.F90:4: warning: Reached end of file while still inside a (nested) comment. Nesting level 1 (probable line reference: 2, 2) ``` even though Fortran has no nested comments, and certainly doesn't have `/*` as comment signs. So message can be ignored.
-rw-r--r--src/commentcnv.l2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/commentcnv.l b/src/commentcnv.l
index 2cf1a39..036f830 100644
--- a/src/commentcnv.l
+++ b/src/commentcnv.l
@@ -1167,7 +1167,7 @@ void convertCppComments(BufStr *inBuf,BufStr *outBuf,const char *fileName)
warn(yyextra->fileName,ctx->lineNr,"Conditional section%sdoes not have "
"a corresponding \\endcond command within this file.",sectionInfo.data());
}
- if (yyextra->nestingCount>0 && yyextra->lang!=SrcLangExt_Markdown)
+ if (yyextra->nestingCount>0 && yyextra->lang!=SrcLangExt_Markdown && yyextra->lang!=SrcLangExt_Fortran)
{
QCString tmp= "(probable line reference: ";
bool first = TRUE;