Reached end of file while still insided a (nested) comment in Markdown (Origin: bugzilla #735584)

[doxygen]

status RESOLVED severity normal in component build for ---
Reported in version 1.8.8 on platform Other
Assigned to: Dimitri van Heesch

On 2014-08-28 10:39:03 +0000, Philipp wrote:

We specify documented directory paths to be in italics. A directory specified like this:

Directory/Subdirectory/

results in the following warning:

warning : Reached end of file while still inside a (nested) comment. Nesting level 2 (probable line reference: 36, 1)

On 2014-08-28 12:11:16 +0000, Philipp wrote:

Using Directory/Subdirectory/ instead of Directory/Subdirectory/ is a working (and acceptable) workaround.

On 2014-11-29 19:24:39 +0000, albert wrote:

What was your file type and how was the code written in it (C-style? as in that case /* is seen as the start of a, nested, comment and takes higher precedence than the markdown comment).

Can you attach a small self contained example that shows your problem so it can be verified that this indeed the case (Example in zip or tar file including used Doxyfile)

On 2014-12-02 08:40:38 +0000, Philipp wrote:

The file type is a plain text Markdown file (not a code file), in our case with an .md file extension.

A simple .md file with the following contents demonstrates the bug:

c:/demo/bug/

On 2014-12-08 14:29:41 +0000, albert wrote:

I think this bug might also have to do with bug_683115.

The code in commentcnv.l (currently line 1014 in subroutine convertCppComments) reads:
if (g_nestingCount>0 || (YY_START==CComment && g_lang!=SrcLangExt_Markdown))
shouldn't this read:
if (g_nestingCount>0 && (YY_START==CComment && g_lang!=SrcLangExt_Markdown))

On 2014-12-19 14:33:19 +0000, Dimitri van Heesch wrote:

Confirmed, it should have simply been

if (g_nestingCount>0 && g_lang!=SrcLangExt_Markdown)

Should be fixed in the next GIT update.

On 2014-12-25 16:03:10 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.9. Please verify if this is indeed the case. Reopen the
bug if you think it is not fixed and please include any additional information
that you think can be relevant (preferrably in the form of a self-contained example).