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 622737 - syntax error on conditional directive spanning multiple lines
syntax error on conditional directive spanning multiple lines
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-06-25 14:48 UTC by Timothy Madden
Modified: 2010-10-09 08:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Sample source, doxyfile, output (68.21 KB, application/octetstream)
2010-06-25 14:49 UTC, Timothy Madden 		Details

Description Timothy Madden 2010-06-25 14:48:25 UTC 
Processing conditional directives on multiple lines produces warnings that end with "syntax error". Boost library header files contain many such conditionals.

Trying to process the following file:

#if !defined(BOOST_MPL_CFG_NO_TEMPLATE_TEMPLATE_PARAMETERS) \
    && ( defined(BOOST_NO_TEMPLATE_TEMPLATES) \
      || BOOST_WORKAROUND( __BORLANDC__, BOOST_TESTED_AT( 0x590) ) \
       )

#   define BOOST_MPL_CFG_NO_TEMPLATE_TEMPLATE_PARAMETERS

#endif

will output

"D:/Local/Projects/ss/ttp.hpp(5) : warning: preprocessing issue while doing constant expression evaluation: syntax error"


Attached are the simple source file, with the Doxyfile and the generated output
Comment 1 Timothy Madden 2010-06-25 14:49:23 UTC 
Created attachment 164627 [details]
Sample source, doxyfile, output
Comment 2 Dimitri van Heesch 2010-07-10 18:48:08 UTC 
Confirmed. Should be fixed in the next subversion update.

As a workaround you can set the following:

ENABLE_PREPROCESSING   = YES
MACRO_EXPANSION        = YES
EXPAND_ONLY_PREDEF     = YES
PREDEFINED             = BOOST_WORKAROUND(x,y)=0
Comment 3 Dimitri van Heesch 2010-10-09 08:19:50 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.2. 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.