After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 652188 - Certain comments can stop doxygen parsing rest of file
Certain comments can stop doxygen parsing rest of file
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.4
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-06-09 13:11 UTC by o.ehlert
Modified: 2011-08-14 14:04 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Zip with files including source code with error causing comment line (35.97 KB, application/octet-stream)
2011-06-09 13:11 UTC, o.ehlert 		Details

Description o.ehlert 2011-06-09 13:11:44 UTC 
Created attachment 189545 [details]
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).
Comment 1 Dimitri van Heesch 2011-06-09 21:15:25 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2011-08-14 14:04:49 UTC 
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.