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 301895 - Support for D debug/version conditionals
Support for D debug/version conditionals
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: general
1.4.x
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks: 173045
 
 
Reported: 2005-04-25 10:31 UTC by Stewart Gordon
Modified: 2018-07-30 10:13 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stewart Gordon 2005-04-25 10:31:26 UTC
The D language supports conditional compilation using debug and version blocks.
 They look like this:

    debug { ... }
    debug (xyz) { ... }
    debug (123) { ... }
    version (xyz) { ... }
    version (123) { ... }

The braces are optional - debug and version can also apply to a single statement
or declaration.  Moreover, any of these can also have 'else' blocks following.

Doxygen doesn't recognise this feature of D at present, and so contents of debug
or version blocks are not documented.

It will be necessary to provide a means in Doxygen of setting which
debug/version identifiers are conditioned in.  A start would be to map them by
some prefix to the space of preprocessor macros.  But better still would be to
add new tags to Doxygen for these.

Note also the special meaning of numeric debug/version identifiers - they are
compiled in iff a greater or equal version level is specified at compile time. 
This behaviour should carry forward to Doxygen.
Comment 1 André Klapper 2018-07-30 10:13:49 UTC
As discussed in https://github.com/doxygen/doxygen/pull/734 , Doxygen has moved its issue tracking to 

   https://github.com/doxygen/doxygen/issues

All Doxygen tickets in GNOME Bugzilla have been migrated to Github. You can subscribe and participate in the new ticket in Github. You can find the corresponding Github ticket by searching for its Bugzilla ID (number) in Github.

Hence I am closing this GNOME Bugzilla ticket.
Please use the corresponding ticket in Github instead. Thanks a lot!