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 769552 - doxygen warning parsing C++11 "using" declaration
doxygen warning parsing C++11 "using" declaration
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.11
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2016-08-05 12:21 UTC by Peter Klotz
Modified: 2017-01-19 21:00 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Example showing the warning (3.13 KB, application/gzip)
2016-08-05 12:21 UTC, Peter Klotz 		Details

Description Peter Klotz 2016-08-05 12:21:35 UTC 
Created attachment 332798 [details]
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<int>>;

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

  using Y=std::map<int,std::list<int> >;
Comment 1 Peter Klotz 2016-08-05 16:30:16 UTC 
Aside from the warning the generated documentation is incorrect.

">>" case (incorrect):

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

"> >" case (correct):

typedef std::map< int, std::list< int > > a::Y
Comment 2 Dimitri van Heesch 2016-12-26 09:07:39 UTC 
Confirmed. Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2016-12-29 18:45:43 UTC 
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).
Comment 4 Peter Klotz 2017-01-19 21:00:11 UTC 
Verified: The bug is fixed in Doxygen 1.8.13. The warning is no longer emitted.