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

namespace named 'internal' confuses doxygen (Origin: bugzilla #590712) #3473

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.5.9 on platform Other
Assigned to: Dimitri van Heesch

On 2009-08-04 08:39:22 +0000, Joachim Reichel wrote:

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?

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.

On 2009-08-04 09:15:56 +0000, Joachim Reichel wrote:

I should have added to the original report that the wrong output is on the "foo.cpp File Reference" page.

On 2009-08-14 12:47:41 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2009-08-20 10:12:52 +0000, Dimitri van Heesch wrote:

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).

@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