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

C++11 scoped enums with same name inside different classes are merged if using tagfile [with test case] (Origin: bugzilla #739210) #5668

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2014-10-26 15:23:51 +0000, Vladimír Vondruš wrote:

Created attachment 289351
Repro/test case

See attached ZIP file for minimal repro case. Generate the tagfile and process it using the following commands:

doxygen Doxyfile.original
doxygen Doxyfile.current

The first command generates original.tag file, the second parses it and produces HTML docs. The documentation for B::Flag enum contains members from A::Flag enum (ReadOnly), but it shouldn't, as the enums are in completely different scope.

This doesn't happen when using C++03 unscoped enums (enum Flag) or when the enums aren't class members (e.g. one part of namespace A, one part of namespace B). It also doesn't happen when both struct A and struct B are parsed as part of one project, so it seems that the needed information is not parsed properly from the tagfile.

Tested with current Git (a31c9ff), but the issue appears for some time (I think it was present already in 1.7).

On 2014-12-22 19:19:02 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2014-12-25 16:03:30 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.9. 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 (preferrably in the form of a self-contained example).

@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