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

Too greedy behavior of @ref const matching (Origin: bugzilla #776988) #6141

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

On 2017-01-07 16:42:37 +0000, Vladimír Vondruš wrote:

Running Doxygen (version doesn't matter) on the following snippet:

/**
@brief A class

See @ref A::A() constructor for details.
*/
class A {
    /** @brief Constructor with the details */
    A();
};

Produces the following warning:

a.cpp:2: warning: unable to resolve reference to `A::A() const' for \ref command

(Yes, it may seem like a really bad improbable corner case case but it really occurred to me in practice a few times.) Currently I'm working around this by providing explicit link text in "", but it would be nice if I wouldn't need to. Suggested solution could be to match const only if it is a complete word and not a prefix.

Thanks a lot!

On 2017-01-17 20:37:03 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2017-12-25 18:43:45 +0000, Dimitri van Heesch wrote:

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