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

Closed
opened this Issue Jul 2, 2018 · 0 comments

Projects
None yet
1 participant
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).