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 663101 - Failure when C++ members defined using macros
Failure when C++ members defined using macros
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.5.1-SVN
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-10-31 13:46 UTC by Neil Bird
Modified: 2011-12-03 18:22 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Unpack to /tmp, then run 'doxygen /tmp/doxygen/Doxyfile'. (18.92 KB, application/x-compressed-tar)
2011-10-31 13:46 UTC, Neil Bird
Details

Description Neil Bird 2011-10-31 13:46:07 UTC
Created attachment 200334 [details]
Unpack to /tmp, then run 'doxygen /tmp/doxygen/Doxyfile'.

This seems to rear its ugly head every so often, so I suspect you're tempted to ban the use of macros in doxygen input!

Attached is a C++ example that defines a member using a macro, and then the use of the macro causes an error, even though macro expansion is enabled (unless I've broken the example):

/tmp/doxygen/src/Cell.h:15: warning: Found ';' while parsing initializer list! (doxygen could be confused by a macro call without semicolon)



Unpack the attachment to /tmp; example tested on Linux, CentOS 5 doxygen 1.7.5.1-20111027.

This is a cut-own example of one of a dozen or so instances of this we see on our code base, not all using the same macro.  Often, the macro is parsed correctly.
Comment 1 Dimitri van Heesch 2011-11-21 16:41:29 UTC
No, I'm still trying to improve macro support, without making doxygen really slow. Hopefully I'm nearly there ;-)

I found the problem. Should be corrected in the next subversion update.
Comment 2 Dimitri van Heesch 2011-12-03 18:22:40 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.6. 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.