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

Missing link for item inside the same namespace (Origin: bugzilla #729063) #5462

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 build for ---
Reported in version 1.8.8 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2014-04-27 14:53:41 +0000, David Mercklé wrote:

Consider the following piece of cpp code. The problem is described as a comment inside the code.


/// this is the global namespace
namespace Namespace{

// uncomment to make the bug disappear :
//using namespace Namespace;

/// this is a struct
struct Struct
{
};

/// this is a class
class Class
{
public:
/// A function
///
/// Detailed description
static void function( Struct s); // correct : link to Struct is present in the function documentation
};

/// A function in the namespace
///
/// Detailed description
void function( Struct s); // BUG : link to Struct is missing in the Function Documentation !

}

The missing link bug is illustrated HERE ("Struct" is not clickable, when it should be) :

http://prenomstat.com/doxygenNsLinkBug/namespace_namespace.html#a5d888a5b4762a99391bc79460452a662

Strangely enough :

  • Within a class instead of a namespace, this problem does not appear
  • The problem disappears when writing "using namespace Namespace;" after starting "namespace Namespace {" !! But of course this is not clean at all.

This problem has been observed with doxygen 1.8.6 and 1.8.7.

Hope you will find a solution.

On 2014-11-17 03:03:55 +0000, Kevin McBride wrote:

Created attachment 290827
Test Case

A sample project was not provided but with version 1.8.8 I was able to reproduce this bug. Attached is a sample project with the basic Doxyfile generated by "doxygen -g"

On 2014-12-23 15:42:30 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2014-12-25 16:03:14 +0000, Dimitri van Heesch wrote:

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

@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