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 172789 - Doxygen doesn't recognise attribute blocks in D
Doxygen doesn't recognise attribute blocks in D
Status: RESOLVED OBSOLETE
Product: doxygen
Classification: Other
Component: build
1.4.x
Other All
: Normal major
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
[moved_to_github]
Depends on:
Blocks: 173045
 
 
Reported: 2005-04-06 11:07 UTC by Stewart Gordon
Modified: 2018-07-30 10:33 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Stewart Gordon 2005-04-06 11:07:05 UTC
Please describe the problem:
The D language has attribute blocks of the form

public {
    ...
}

containing declarations at the module or class level.  Doxygen doesn't see these.

Steps to reproduce:
Create a D file that uses attribute blocks.  Example:

class Qwert {
    public {
        int yuiop() { ... }
    }
}

Try running it through doxygen.

Actual results:
Doxygen fails to see the method yuiop.

Expected results:
Seen and documented the function yuiop, and that it is a public method. 
Generally needs to work with all attributes.

Does this happen every time?
Yes

Other information:
Comment 1 Stewart Gordon 2005-06-09 16:43:52 UTC
It should be noted that there are five access attributes in D: export, public,
protected, package and private.
Comment 2 André Klapper 2018-07-30 10:33:22 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!