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

@cond broken in current SVN (Origin: bugzilla #690418) #4997

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

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

On 2012-12-18 14:15:37 +0000, Haffmans wrote:

The @cond command is broken for me in the current SVN version (r834). The sample in the manual (http://www.stack.nl/~dimitri/doxygen/commands.html#cmdcond) now behaves reversed. Sections that are enabled are hidden, sections that are not enabled are shown.

Changing the @cond conditions with ! as a prefix (e.g. "@cond !DEV") makes it work again, but that too is counter-intuitive.

I'm not sure if this was introduced by bug # 683215 or perhaps # 630645, but they seem to be related.

The command works fine in the latest stable release.

On 2012-12-19 10:09:02 +0000, Dimitri van Heesch wrote:

Confirmed. A new expression parser was introduced, but the behaviour of @cond should not have changed. Will be corrected.

On 2012-12-26 16:09:09 +0000, Dimitri van Heesch wrote:

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