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

links to typedefs go to the source of the typedef instead (Origin: bugzilla #584194) #3410

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

On 2009-05-29 10:18:54 +0000, Joachim Reichel wrote:

Steps to reproduce:

/// template vector class
template
class Vector { };

/** \defgroup typedefs Typedefs */

/// vector with floats
/// \ingroup typedefs
typedef Vector FloatVector;

/// vector with doubles
/// \ingroup typedefs
typedef Vector DoubleVector;

/// some class
class MyClass
{
public:
/// some method
void foo (FloatVector&);
};

Actual results:

The FloatVector parameter of MyClass::foo() links to Vector (such that the user does not know how FloatVector relates to Vector).

Expected results:

The FloatVector parameter of MyClass::foo() should link to typedef of FloatVector.

Observed with the default config file of doxygen 1.5.9

On 2010-06-09 07:49:11 +0000, Joachim Reichel wrote:

This bug still exists in doxygen 1.6.3.

On 2010-06-29 08:51:01 +0000, Joachim Reichel wrote:

This bug still exists in doxygen 1.7.1.

On 2010-10-11 09:26:05 +0000, Joachim Reichel wrote:

This bug still exists in doxygen 1.7.2.

On 2010-11-10 16:51:46 +0000, Joachim Reichel wrote:

If "#FloatVector" appears in running text (e.g. documentation of foo()), then it gets linked to the typedef of FloatVector as expected. However, as parameter of foo() it gets linked to Vector (as reported initially).

BTW why does "FloatVector" (without #) not get linked automatically?

On 2011-01-12 08:22:17 +0000, Joachim Reichel wrote:

This bug still exists in doxygen 1.7.3.

On 2011-03-31 13:47:13 +0000, Joachim Reichel wrote:

This bug still exists in doxygen 1.7.4.

On 2011-08-15 07:37:44 +0000, Joachim Reichel wrote:

Fixed in 1.7.5.

On 2013-01-03 10:06:27 +0000, Kjell Ahlstedt wrote:

*** Bug 659249 has been marked as a duplicate of this bug. ***

@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