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

broken namespace and class list using nested C++ namespaces (Origin: bugzilla #679631) #4789

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2012-07-09 13:47:18 +0000, wrote:

Created attachment 218337
A couple of C++ headers and doxyfile config that cause the problem described above.

If classes are included into a nested namespace structure, and namespace documentation is provided only for inner namespace(s), the undocumented outer namespace(s) cause the internal namespace(s)/class(es) not to appear neither in the namespace nor in the class list. BTW, classes appear correctly into the "Class index" page.

On 2012-07-15 14:11:30 +0000, Dimitri van Heesch wrote:


Found the problem. Here is a patch against the latest SVN that you could try:

--- index.cpp.orig 2012-07-12 22:37:55.000000000 +0200
+++ index.cpp 2012-07-15 16:06:55.000000000 +0200
@@ -1402,7 +1402,7 @@
NamespaceDef *cnd;
for (cnli.toFirst();(cnd=cnli.current());++cnli)

  •  if (cnd->isLinkable() && cnd->localName().find('@')!=-1)
  •  if (cnd->isLinkable() && cnd->localName().find('@')==-1)
       return TRUE;

On 2012-08-11 13:18:21 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.2. 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.

@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