summaryrefslogtreecommitdiffstats
path: root/src/scanner.l
diff options
context:
space:
mode:
authoralbert-github <albert.tests@gmail.com>2019-07-10 16:48:53 (GMT)
committeralbert-github <albert.tests@gmail.com>2019-07-10 16:48:53 (GMT)
commitef5af7618fbec3ac240e7a1099607d9ff2b3cc4f (patch)
tree5bc4d92c249745a79ab3661a1c8cb1c32d8b146b /src/scanner.l
parent34c9bac4624c5b94172af4a9d9168a44482fe552 (diff)
downloadDoxygen-ef5af7618fbec3ac240e7a1099607d9ff2b3cc4f.zip
Doxygen-ef5af7618fbec3ac240e7a1099607d9ff2b3cc4f.tar.gz
Doxygen-ef5af7618fbec3ac240e7a1099607d9ff2b3cc4f.tar.bz2
Problem with with comment recognition for group open and closing commands
Besides the wanted start of comments `//!`, `///`, `/*!` and `/**` also the "normal" comments `//` and `/*` were recognized as starting a comment for the group open (`\{`, `@{`) and group closing (`\}`, `@}`) commands. This was due to the usage of `?` in the regular expression meaning 0 or 1 times.
Diffstat (limited to 'src/scanner.l')
-rw-r--r--src/scanner.l4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/scanner.l b/src/scanner.l
index 42058d8..ea19382 100644
--- a/src/scanner.l
+++ b/src/scanner.l
@@ -2849,7 +2849,7 @@ OPERATOR "operator"{B}*({ARITHOP}|{ASSIGNOP}|{LOGICOP}|{BITOP})
}
}
-<FindMembers,FindFields>("//"([!/]?){B}*{CMD}"{")|("/*"([!*]?){B}*{CMD}"{") {
+<FindMembers,FindFields>("//"([!/]){B}*{CMD}"{")|("/*"([!*]){B}*{CMD}"{") {
//handleGroupStartCommand(current->name);
if (previous && previous->section==Entry::GROUPDOC_SEC)
{
@@ -2901,7 +2901,7 @@ OPERATOR "operator"{B}*({ARITHOP}|{ASSIGNOP}|{LOGICOP}|{BITOP})
}
}
}
-<FindMembers,FindFields,ReadInitializer>"//"([!/]?){B}*{CMD}"}".*|"/*"([!*]?){B}*{CMD}"}"[^*]*"*/" {
+<FindMembers,FindFields,ReadInitializer>"//"([!/]){B}*{CMD}"}".*|"/*"([!*]){B}*{CMD}"}"[^*]*"*/" {
bool insideEnum = YY_START==FindFields || (YY_START==ReadInitializer && lastInitializerContext==FindFields); // see bug746226
closeGroup(current,yyFileName,yyLineNr,insideEnum);
}