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

Bogus warning regarding nested comments (Origin: bugzilla #746614) #5768

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2015-03-22 17:51:15 +0000, albert wrote:

Created attachment 300085
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: )

On 2015-03-22 17:55:40 +0000, albert wrote:

I've just pushed a proposed patch to github (pull request 320)

On 2015-03-22 18:23:22 +0000, albert wrote:

Patch has been integrated in github.

On 2015-06-27 19:01:52 +0000, Dimitri van Heesch wrote:

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).

On 2015-07-15 13:52:39 +0000, albert wrote:

Bogus message is gone.

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment