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 746614 - Bogus warning regarding nested comments
Bogus warning regarding nested comments
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: build
1.8.9.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2015-03-22 17:51 UTC by albert
Modified: 2015-07-15 13:52 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Project to reproduce problem (26.76 KB, application/x-gzip)
2015-03-22 17:51 UTC, albert 		Details

Description albert 2015-03-22 17:51:15 UTC 
Created attachment 300085 [details]
Project to reproduce problem

In case the previous file gives a warning regarding the wrong used nested comments and the next file does not have any doxygen comment there is still the message that there is a nested comment but even without probable line numbers.
Warnings look like:
.../aa.c:18: warning: Reached end of file while still inside a (nested) comment. Nesting level 4 (probable line reference: 13, 11, 10, 8)
.../bb.c:11: warning: Reached end of file while still inside a (nested) comment. Nesting level 4 (probable line reference: )
Comment 1 albert 2015-03-22 17:55:40 UTC 
I've just pushed a proposed patch to github (pull request 320)
Comment 2 albert 2015-03-22 18:23:22 UTC 
Patch has been integrated in github.
Comment 3 Dimitri van Heesch 2015-06-27 19:01:52 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.10. 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 (preferably in the form of a self-contained example).
Comment 4 albert 2015-07-15 13:52:39 UTC 
Bogus message is gone.