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 679631 - broken namespace and class list using nested C++ namespaces
broken namespace and class list using nested C++ namespaces
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.8.1.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2012-07-09 13:47 UTC by lorentztztz
Modified: 2012-08-11 13:18 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
A couple of C++ headers and doxyfile config that cause the problem described above. (22.52 KB, application/x-zip-compressed)
2012-07-09 13:47 UTC, lorentztztz 		Details

Description lorentztztz 2012-07-09 13:47:18 UTC 
Created attachment 218337 [details]
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.
Comment 1 Dimitri van Heesch 2012-07-15 14:11:30 UTC 
Confirmed.

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;
       }
Comment 2 Dimitri van Heesch 2012-08-11 13:18:21 UTC 
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.