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

Nested namespace causes incorrect display when referenced via .tag file (Origin: bugzilla #705499) #5258

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2013-08-05 11:59:33 +0000, diarmuid.kieran@pdgm.com wrote:

Created attachment 250860
Screenshot of doxygen doc for TestProject1

I created two projects - TestProject1 and TestProject2


TestProject1

Contains 1 header file, as follows:

XBO.h

/*! \brief XBO is boring
*/
namespace XBO {

/*! \brief XBONestedNS is also boring
*/

namespace XBONestedNS {
}

}

After running this file through doxygen, I get a tag file in the resulting documentation directory as follows:

XBO namespaceXBO.html XBO::XBONestedNS XBO::XBONestedNS namespaceXBO_1_1XBONestedNS.html TestProject1 /abc1/users/someuser/userbranch/project/src/library/TestProject1/ dir_a1513fb003dc8c1062e5770a29b83379.html XBO.h

TestProject2

Contains 1 header file, as follows

YBO.h

/*! \brief YBO is boring
*/
namespace YBO {
}

In the makefile.doxygen for TestProject2, the .tag file from TestProject1 is referenced, as follows:

@TAGFILES = $(DOXY_OUTPUT)/../TestProject1/TestProject1.tag=../TestProject1

When the doxygen files for TestProject2 are created, the namespace XBO (from TestProject1) is erroneously contained in the namespace list for TestProject2.

In other words, when a project is referenced by another project and that projected contains a nested namespace, the top level namespace of the first project (ie the namespace within which is nested a namespace) is displayed in the doxygen documentation of the second project.

Screenshots of the documentation generated for TestProject1 and TestProject2 are attached.

On 2013-08-05 12:02:04 +0000, diarmuid.kieran@pdgm.com wrote:

Created attachment 250862
Screenshot of doxygen doc for TestProject2

The namespace XBO from TestProject1 is mysteriously in the list of namespaces for TestProject2

On 2014-01-05 10:47:30 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2014-04-21 10:09:14 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.7. 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 (preferrably in the form of a self-contained example).

On 2014-04-24 07:28:16 +0000, diarmuid.kieran@pdgm.com wrote:

How can I verify this? Doxygen 1.8.7 is not available yet. Only 1.8.6 is on the Doxygen site.

On 2014-04-24 09:51:00 +0000, diarmuid.kieran@pdgm.com wrote:

I saw that SourceForge had Doxygen 1.8.7, so I downloaded that. However, some of the images (for example the namespace "N" image, are missing when I generate the documentation, so I don't know if that is the correct 1.8.7 package.

@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