Skip to content
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

[PATCH] c++ scanner bug: group end marker eats up following sentences in the line (Origin: bugzilla #658033) #4391

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

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2011-09-02 07:01:43 +0000, matsu@users.sourceforge.net wrote:

Created attachment 195455
patch fixing this bug.

In scanner.l, group end marker is defined like following (simplified):

"/* @}"."/"

Unfortunately, it matches multiple c-comment blocks.

When using macros, this trouble especially becomes a problem.

For example, the following codes define a common member functions
of the class by the macro.

#define COMMON_MEMBER_FUNCTIONS(klass)
public:
/** @name constructors /
/
@{ /
klass();
/
@} /
/
* @name common functions /
/
@{ /
void func();
/
@} */

class Class {
COMMON_MEMBER_FUNCTIONS(Class)
};

Macro is expanded in single-line by preprocessor, so, func() is lost,
and it is not described in generated documents.

Attached patch fixes this bug.

My best regards.

On 2011-09-02 08:15:47 +0000, matsu@users.sourceforge.net wrote:

The sample code previously enumerated seems to cause another bug too.
It is necessary to comment on the Qt style to make only the reported bug appear.

#define COMMON_MEMBER_FUNCTIONS(klass)
public:
/*! @name constructors /
/
@{ /
klass();
/
@} /
/
! @name common functions /
/
@{ /
void func();
/
@} */

class Class {
COMMON_MEMBER_FUNCTIONS(Class)
};

On 2011-09-29 19:54:21 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2011-12-03 18:22:53 +0000, Dimitri van Heesch wrote:

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.

@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
You can’t perform that action at this time.