New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Function macro improperly parsed with escaped new line (Origin: bugzilla #624014) #3840

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.7.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2010-07-10 06:19:44 +0000, Charles wrote:

Created attachment 165598
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;

On 2010-07-10 06:26:44 +0000, Charles wrote:

Created attachment 165599
doxygen configuration file

use this configuration file with the test.C file.

doxygen command

doxygen -d Preprocessor

cpp command

cpp test.C

On 2010-07-10 17:19:54 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2010-07-12 13:36:20 +0000, Charles wrote:

(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

On 2010-07-12 15:38:35 +0000, Dimitri van Heesch wrote:

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.

On 2010-10-09 08:19:12 +0000, Dimitri van Heesch wrote:

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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment