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 590712 - namespace named 'internal' confuses doxygen
namespace named 'internal' confuses doxygen
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.5.9
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-08-04 08:39 UTC by Joachim Reichel
Modified: 2009-08-20 10:12 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Joachim Reichel 2009-08-04 08:39:22 UTC
Please describe the problem:
Doxygen produces wrong output if there is a namespace of name 'internal'.

Steps to reproduce:
/// \file

/// internal namespace
namespace internal {

/// struct Foo
struct Foo {};

} // namespace internal

/// typedef Bar
typedef internal::Foo Bar;

Doxyfile: default of 1.5.9


Actual results:
Bar is listed as variable(!) without type and name "__pad0__".

Expected results:
That Bar gets documented as typedef to internal::Foo.

Does this happen every time?
Yes.

Other information:
The problem disappears if the namespace is renamed or "typedef internal" is replaced by "typedef ::internal". Similar if there is an outer namespace and "typedef internal" is replaced by "typedef outer::internal". The problem with the second workaround is that there is no warning/error and one has to search the documentation to detect these problems.
Comment 1 Joachim Reichel 2009-08-04 09:15:56 UTC
I should have added to the original report that the wrong output is on the "foo.cpp File Reference" page.
Comment 2 Dimitri van Heesch 2009-08-14 12:47:41 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 3 Dimitri van Heesch 2009-08-20 10:12:52 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.0. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).