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 @ref or @link C++ operator overloads (Origin: bugzilla #707431) #5284

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

On 2013-09-03 23:28:02 +0000, Tim wrote:

See my post on stack overflow for all the details:

http://stackoverflow.com/questions/18479768/referencing-c-operator-overloads-with-doxygen

On 2013-09-04 09:21:44 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-12-24 18:59:33 +0000, Dimitri van Heesch wrote:

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

On 2015-12-12 01:37:18 +0000, Andrew wrote:

Still doesn't work for templates. If in the original example on stack overflow template is placed before class Foo definition, the problem reoccurs. I tried @ref on regular member functions, they work fine but the overloaded operators do not. The same is valid for @link. Tested on doxygen versions 1.8.9.1 and 1.8.10.

On 2015-12-12 08:40:37 +0000, Dimitri van Heesch wrote:

I couldn't immediate reproduce this based on your description. Can you please file a new bug report and attach a self-contained example (source+config file in a tar or zip) that allows me to reproduce the problem?

@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