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

unnamed class results in copy_doc not finding target in totally unrelated files (Origin: bugzilla #608359) #3653

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

Original attachment names and IDs:

On 2010-01-28 17:28:40 +0000, Torsten Robitzki wrote:

Created attachment 152501
reproducer

This might seem a little esoteric, but this is real code and it was quit hard to find what was triggering the bug. The attached file copy_doc.h contains a little example that reproduces the bug and I've used Comeau C/C++ Online to make sure, that this is valid C++.

The two classes data::abs_interface and data::totally_unrelated and the object foo might be in parts of the project that seems to be totally unrelated. When I implement the interface data::abs_interface with an unnamed class, this will cause doxygen to not find the @copydoc target in class data::totally_unrelated.

A working workaround is to give the class of foo a name.

best regards
Torsten

On 2010-01-28 17:29:13 +0000, Torsten Robitzki wrote:

Created attachment 152502
doxyfile

On 2010-03-18 21:03:02 +0000, Torsten Robitzki wrote:

I've debug the issue a little bit and what I've found so far is, that the anonymous class gets added as a class named "@0::data" and this seems to hide data::totally_unrelated when the copydoc command looks up f1().

On 2010-04-20 12:24:29 +0000, Dimitri van Heesch wrote:

Confirmed. This should be corrected in the latest subversion update.

On 2010-06-15 11:22:16 +0000, Dimitri van Heesch wrote:

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

@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