summaryrefslogtreecommitdiffstats
path: root/src/doctokenizer.l
diff options
context:
space:
mode:
authoralbert-github <albert.tests@gmail.com>2019-05-30 11:50:14 (GMT)
committeralbert-github <albert.tests@gmail.com>2019-05-30 11:50:14 (GMT)
commit31a668c8c8ad29119158b140c34f67940dfeb7ed (patch)
tree8aafe5870c5d188e26464253a3921dbf0881280c /src/doctokenizer.l
parentf652aa496cd26f3c835a240b9b6abc14437309e5 (diff)
downloadDoxygen-31a668c8c8ad29119158b140c34f67940dfeb7ed.zip
Doxygen-31a668c8c8ad29119158b140c34f67940dfeb7ed.tar.gz
Doxygen-31a668c8c8ad29119158b140c34f67940dfeb7ed.tar.bz2
Conflict between RCS tag and (e.g.) php description
In some languages the `$` is used to start a variable name (php, perl). When having a description like: ``` <b>$RRDp::error_mode</b>, <b>$RRDp::error</b> ``` this will lead to a message like: ``` warning: found </b> at different nesting level (4) than expected (2) ``` because the part `$RRDp:` is seen as start of a RCS tag and runs till the next `$`. Though the `::` indicates here a class / namespace separator and in case of `$...:` directly followed by a `:` this should not be seen as RCS tag.
Diffstat (limited to 'src/doctokenizer.l')
-rw-r--r--src/doctokenizer.l2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doctokenizer.l b/src/doctokenizer.l
index 7b402ca..e4c2f28 100644
--- a/src/doctokenizer.l
+++ b/src/doctokenizer.l
@@ -658,7 +658,7 @@ REFWORD_NOCV {FILEMASK}|{LABELID}|{REFWORD2_NOCV}|{REFWORD3}|{REFWORD4_NOCV}
g_token->isEMailAddr=TRUE;
return TK_URL;
}
-<St_Para>"$"{ID}":"[^\n$]+"$" { /* RCS tag */
+<St_Para>"$"{ID}":"[^:\n$][^\n$]*"$" { /* RCS tag */
QCString tagName(yytext+1);
int index=tagName.find(':');
g_token->name = tagName.left(index);