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

Cannot make unscoped link to C++ conversion operator [with test case] (Origin: bugzilla #739214) #5670

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

Original attachment names and IDs:

On 2014-10-26 16:28:31 +0000, Vladimír Vondruš wrote:

Created attachment 289356
Repro/test case

See attached ZIP file for minimal repro case or the following snippet:

 * @brief Foo
 * - operator int()
 * - @ref operator int()
 * - @ref operator int() "title"
 * - Foo::operator int()
 * - @ref Foo::operator int()
 * - @ref Foo::operator int() "title"
struct Foo {
    /** @brief Conversion to int */
    operator int();

The generated HTML docs properly parse and document the int conversion operator, but none of the first three links work. The first one is not detected as link at all (no warning on output), the second and third produce a warning:

operator.h:3: warning: unable to resolve reference to `operator' for \ref command
operator.h:4: warning: unable to resolve reference to `operator' for \ref command

Interestingly enough, the second three (explicitly scoped) links work without issue, so that can be considered as workaround.

All other kinds of unscoped operator links (operator=(), operator[]() etc.) are working without issues. I admit that marking the conversion operator link implicit might bring up many false positives, so I'm all for making these links possible only with explicit @ref. Possibly related issues: # 678643, # 699465.

Tested with current Git (a31c9ff).

On 2014-11-16 15:50:32 +0000, Dimitri van Heesch wrote:

I'll follow your suggestions. Should be corrected in the next GIT update.

On 2014-11-16 19:29:37 +0000, Vladimír Vondruš wrote:

Just tested and works, thanks!

@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