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

doxygen warning parsing C++11 "using" declaration (Origin: bugzilla #769552) #6044

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2016-08-05 12:21:35 +0000, Peter Klotz wrote:

Created attachment 332798
Example showing the warning

The attached test case produces this warning:

/home/user/TestCase/Source/private.hpp:3: warning: documented symbol `typedef a::std::map< int, std::list< int >> Y' was not declared or defined.

The problem has its origin in a C++11 "using" declaration that appears twice (but identical) in the code.

The warning occurs if the using declaration looks like this:

using Y=std::map<int,std::list>;

It disappears if it is written like this (note "> >" instead of ">>"):

using Y=std::map<int,std::list >;

On 2016-08-05 16:30:16 +0000, Peter Klotz wrote:

Aside from the warning the generated documentation is incorrect.

">>" case (incorrect):

using a::Y = typedef std::map<int,std::list>

"> >" case (correct):

typedef std::map< int, std::list< int > > a::Y

On 2016-12-26 09:07:39 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2016-12-29 18:45:43 +0000, Dimitri van Heesch wrote:

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

On 2017-01-19 21:00:11 +0000, Peter Klotz wrote:

Verified: The bug is fixed in Doxygen 1.8.13. The warning is no longer emitted.

@doxygen doxygen closed this Jul 19, 2018

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