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 690418 - @cond broken in current SVN
@cond broken in current SVN
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.2-SVN
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-12-18 14:15 UTC by Haffmans
Modified: 2012-12-26 16:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Haffmans 2012-12-18 14:15:37 UTC 
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.
Comment 1 Dimitri van Heesch 2012-12-19 10:09:02 UTC 
Confirmed. A new expression parser was introduced, but the behaviour of @cond should not have changed. Will be corrected.
Comment 2 Dimitri van Heesch 2012-12-26 16:09:09 UTC 
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.