-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Doxygen doesn't correctly treat nested \if statements #9779
Comments
Problem is also present when using |
Renewed implementation of the `\if ...\endif` structure to better accommodate the nesting of these type of blocks.
I've just pushed a proposed patch, pull request #9789 |
@albert-github: Just to make sure: Shall we test this on our end now? I am just asking because the Build of the pull request wasn't successful. |
That would be much appreciated, you can use the proposed patch at your side (with the current master as base). |
Code has been integrated in master on GitHub (please don't close the issue as this will be done at the moment of an official release). |
@albert-github: I can confirm that this patch does the job! Thanks! |
This issue was previously marked 'fixed but not released', |
Describe the bug
Parts of the documentation of the top level \if statement (enabled vis ENABLED_SECTIONS in the doxyfile) end up in the documentation. This is correct but parts from the \else statement end up being in the output as well. I did test this with 1.9.6 and even 1.8.10. Same result.
Expected behavior
Only the enabled stuff should end up being documented
Screenshots
To Reproduce
I attached a version reproducing the effect. Removing BUILD_WITH_A from the ENABLED_SECTIONS results in correct output. This might be related to the fact that then only the \else branch is touched.
Version
1.9.6 but also 1.8.10
DoxygenIssue.zip
The text was updated successfully, but these errors were encountered: