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 719591 - expand_as_defined macro does not properly work
expand_as_defined macro does not properly work
Status: RESOLVED WONTFIX
Product: doxygen
Classification: Other
Component: general
1.8.5
Other Mac OS
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-11-30 09:47 UTC by Anton
Modified: 2013-12-08 18:48 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Self-explained sample for demonstration (640 bytes, application/x-gzip)
2013-11-30 09:47 UTC, Anton
Details

Description Anton 2013-11-30 09:47:58 UTC
Created attachment 263198 [details]
Self-explained sample for demonstration

EXPAND_AS_DEFINED tag shall (according to the documentation) expand macro (with definition taken from sources) but it doesn't.

Self-explaining sample (with minimal doxyfile) are attached as gzipped tarball.
Comment 1 Dimitri van Heesch 2013-12-08 13:32:47 UTC
Doxygen assumes your header files are guarded against multiple inclusion and are self-contained (i.e. can be placed at the top of a .c file without causing compilation problems). 

This is usually good programming practice. 

Your example does not adhere to these assumptions. It uses a header file as a poor man's template that is expanded differently based on the inclusion context. So this will not work with doxygen, and it is also not clear what output doxygen should produce in such case. 

I'll add a note about this limitation in the documentation.
Comment 2 Kevin McBride 2013-12-08 18:48:35 UTC
Adding "documentation" keyword per comment #1.