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 644864 - Nested anonymous namespaces are reported as being the “cpp” namespace
Nested anonymous namespaces are reported as being the “cpp” namespace
Status: RESOLVED DUPLICATE of bug 639716
Product: doxygen
Classification: Other
Component: general
1.7.3
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2011-03-15 22:47 UTC by Lénaïc Huard
Modified: 2011-03-26 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test case (17.60 KB, application/x-bzip)
2011-03-15 22:47 UTC, Lénaïc Huard
Details

Description Lénaïc Huard 2011-03-15 22:47:14 UTC
Created attachment 183472 [details]
test case

Hello,

Since my update to Doxygen 1.7.3, some anonymous namespaces are reported as being the “cpp” namespace.

The issue can be reproduced with the following cpp file:

===================================================
/**
 * \file
 */

#include "Foo.hpp"

namespace shq
{
  namespace
  {
    void private_function( )
    {
    }
  }
}
===================================================

If there is no “Foo.hpp”, then the function is properly detected as belonging to “shq::anonymous_namespace{Foo.cpp}”.
As soon as there is a “Foo.hpp” file (even empty), the function is detected as belonging to “namespace shq::cpp”.

The bug exists in Doxygen 1.7.3 but didn’t exist in 1.7.1.
Comment 1 Dimitri van Heesch 2011-03-26 12:57:29 UTC
I think this is another instance of the regression there was in handling #includes (see bug 639716). Should be fixed in the next release.

*** This bug has been marked as a duplicate of bug 639716 ***