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

Some external namespaces appear in list despite having ALLEXTERNALS = NO (Origin: bugzilla #712819) #5358

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

On 2013-11-21 14:56:17 +0000, Alex Finch wrote:

I am running doxygen on 66 separate projects using ALLEXTERNALS = NO.
A small number of items appear in the class and namespace listing from external projects. I can't see what is special about these particular items but they are all nested namespaces, i.e.

namespace FRED
namespace JIM

however other examples of nested namespaces work fine.

Although the rogue items appear in listings there is no hyperlink to the relevent documentation.

On 2013-11-23 13:43:38 +0000, Dimitri van Heesch wrote:

It would be very helpful if you could attach a self-contained example that would allow me to reproduce the problem. Is that possible?

On 2013-11-27 11:42:55 +0000, Alex Finch wrote:

After much trial and error it appears that items like this in the tag file:


appear in the listing of namespaces, whereas without the :: they do not. Hope this helps.

On 2013-12-08 15:32:27 +0000, Dimitri van Heesch wrote:

Any idea what causes these kind of namespaces to appear in the tagfile?
Is there an unnamed namespace inside ATestNamespace perhaps?

On 2013-12-24 12:28:37 +0000, Dimitri van Heesch wrote:

I've not been able to reproduce the problem, but I've a found 2 cases where the :: might in theory be added at the end. I've fixed those, so if the next release doesn't solve the problem, I really need a self-contained example that shows the problem to be able to continue.

On 2013-12-24 19:00:03 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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 2013-12-31 15:22:04 +0000, wrote:

I have a similar problem, it is described with an example in bug 705499
I have ran the example I described in that bug report using Doxygen 1.8.6 but I still see the same problem.
If you wish, I can provide you with any additional information you might require to fix it.

@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