Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Certain comments can stop doxygen parsing rest of file (Origin: bugzilla #652188) #4292

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant
Copy link

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2011-06-09 13:11:44 +0000, wrote:

Created attachment 189545
Zip with files including source code with error causing comment line

In our company we have a code editor that uses a lot of comments in the source code to store information about syntax structuring and coloring.

All sources we try to document with doxygen, that have been edited with our code editor, will miss the function part. Doxygen does not generate a documentation of the function section, e.g. caller/callee graphes.

I was able to strip down the problem to a single comment line that is causing the problem:

/* repeat = "\n} while ", "\ndo\n{", "", "\t". */

In case I remove the line, all the documentation will be produced by doxygen.

Please find attached a minimal example I was able to find (including doxyfile and screenshot of wrong/missing output, all done with doxygen 1.7.4).

On 2011-06-09 21:15:25 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2011-08-14 14:04:49 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.5. 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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.