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

@copydoc not working for const member overloads (Origin: bugzilla #707995) #5296

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

Original attachment names and IDs:

On 2013-09-12 21:24:23 +0000, Robert wrote:

Created attachment 254817
Sample that repros the problem

I find difficulty in both automatic link generation and @copydoc
when it comes to 'const' overloaded member methods. Example:

class foo
{
public:
Object* getObject();
Object const* getObject() const;
};

I have JAVADOC_AUTOBRIEF enabled. My documentation for the class above is:

class foo
{
public:
/// Some brief documentation.
/// @return Returns the object.
Object* getObject();

/// @copydoc foo::getObject() const
Object const* getObject() const;
};

The warning I get from Doxygen is:

warning: Found recursive @copybrief or @copydoc relation for argument
'foo::getObject()'.

Attached archive has sample code, documentation output (HTML), doxyconfig file, and more.

Discussion on the issue with Albert on the mailing list:
http://sourceforge.net/mailarchive/message.php?msg_id=31395240

On 2013-09-21 15:51:45 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2013-12-24 18:59:36 +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).

@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