summaryrefslogtreecommitdiffstats
path: root/testing
diff options
context:
space:
mode:
authoralbert-github <albert.tests@gmail.com>2019-10-29 16:21:50 (GMT)
committeralbert-github <albert.tests@gmail.com>2019-10-29 16:21:50 (GMT)
commitc42c0ae66542e4e154c2646fc725890554208d89 (patch)
treed71bc391368a885fa34327be53f8dc40b0a714e4 /testing
parentad9be5fb2339151f1d75a6c9aba4226e48a81ae1 (diff)
downloadDoxygen-c42c0ae66542e4e154c2646fc725890554208d89.zip
Doxygen-c42c0ae66542e4e154c2646fc725890554208d89.tar.gz
Doxygen-c42c0ae66542e4e154c2646fc725890554208d89.tar.bz2
Length of identifying fenced code block
In case we have a problem like: ``` /** \file * ``` * router = (new Router()); * ``` */ ``` there is no problem, but as soon as we add a space somewhere before the start or end identifier of the fenced code block we get: ``` .../aa.h:6: warning: reached end of file while inside a '```' block! The command that should end the block seems to be missing! ``` i.e. a problem like: ``` /** \file * ``` * router = (new Router()); * ``` */ ``` or ``` /** \file * ``` * router = (new Router()); * ``` */ ``` The relevant length is the length identifying the fenced code block / number of back ticks, not the number of spaces in front of it (analogous number of tildes).
Diffstat (limited to 'testing')
0 files changed, 0 insertions, 0 deletions