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 624014 - Function macro improperly parsed with escaped new line
Function macro improperly parsed with escaped new line
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.7.1
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2010-07-10 06:19 UTC by Charles
Modified: 2010-10-09 08:19 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
C++ test case file (116 bytes, application/octet-stream)
2010-07-10 06:19 UTC, Charles 		Details
doxygen configuration file (9.58 KB, text/plain)
2010-07-10 06:26 UTC, Charles 		Details

Description Charles 2010-07-10 06:19:44 UTC 
Created attachment 165598 [details]
C++ test case file

When a function macro definition has a escaped new line character between the macro name and the macro argument list; doxygen parses the macro diffrently then the gnu C++ preprocessor cpp.

e.g.

#define macroFunction\
(var_a, var_b)  \
typedef int var_a##_##var_b##_##int

macroFunction(this, var);


doxygen preprocesses into this


#define macroFunction
00002
00003
00004
00005  (var_a, var_b)  typedef int var_a_var_b_int (this, var);
00006
00007
00008
00009


cpp preprocesses into this


typedef int this_var_int;
Comment 1 Charles 2010-07-10 06:26:44 UTC 
Created attachment 165599 [details]
doxygen configuration file

use this configuration file with the test.C file.

doxygen command

doxygen -d Preprocessor

cpp command

cpp test.C
Comment 2 Dimitri van Heesch 2010-07-10 17:19:54 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 3 Charles 2010-07-12 13:36:20 UTC 
(In reply to comment #2)
> Confirmed. Should be fixed in the next subversion update.

Is there anything further I need to provide or do at this point?

--Charles
Comment 4 Dimitri van Heesch 2010-07-12 15:38:35 UTC 
no, just wait until the next subversion update (it will be announced on the user mailing list) and then verify if the issue is indeed resolved.
Comment 5 Dimitri van Heesch 2010-10-09 08:19:12 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.