diff options
| author | albert-github <albert.tests@gmail.com> | 2019-06-01 12:01:20 (GMT) |
|---|---|---|
| committer | albert-github <albert.tests@gmail.com> | 2019-06-01 12:01:20 (GMT) |
| commit | 962b9c9a85384f358258725767d5ae5a2784a0e8 (patch) | |
| tree | b9c185575a02bad3bfbd7457c3b7503b0ae859f8 /src/scanner.l | |
| parent | 0a15da0120834a5cf7db20843b7d63f3c82f5f5d (diff) | |
| download | Doxygen-962b9c9a85384f358258725767d5ae5a2784a0e8.zip Doxygen-962b9c9a85384f358258725767d5ae5a2784a0e8.tar.gz Doxygen-962b9c9a85384f358258725767d5ae5a2784a0e8.tar.bz2 | |
Correction warning message
When there is a problem with a backticjk comment block we can get the message:
reached end of file while inside a ````' block!
this is a bit unreadable / non understandable as we see see 4 backticks followed by a single quote, it woulb be more readable when we get
reached end of file while inside a '```' block!
Diffstat (limited to 'src/scanner.l')
| -rw-r--r-- | src/scanner.l | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/scanner.l b/src/scanner.l index f94e4f8..2634485 100644 --- a/src/scanner.l +++ b/src/scanner.l @@ -6771,7 +6771,7 @@ OPERATOR "operator"{B}*({ARITHOP}|{ASSIGNOP}|{LOGICOP}|{BITOP}) } <DocCopyBlock><<EOF>> { warn(yyFileName,yyLineNr, - "reached end of file while inside a `%s' block!\n" + "reached end of file while inside a '%s' block!\n" "The command that should end the block seems to be missing!\n", docBlockName.data()); yyterminate(); |