Skip to content
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

Matching of declaration and definition fails (Origin: bugzilla #585543) #3420

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status VERIFIED severity normal in component general for ---
Reported in version 1.5.9 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2009-06-12 10:42:24 +0000, Peter Klotz wrote:

Please describe the problem:
The attached example generates this error message:

Example.hpp:12: Warning: no matching file member found for
std::string n::toString(const std::vector< Tag > &p_tags, const std::string &p_separator="/")
Possible candidates:
std::string toString(const TTags &p_tags, const std::string &p_separator)

Steps to reproduce:

  1. Extract attachment Example.tar.gz
  2. Run doxygen
  3. View Repository.Release.log

Actual results:
Repository.Release.log is not empty.

Expected results:
No warnings should be issued and Repository.Release.log should therefore be empty.

Does this happen every time?
Yes.

Other information:
The slightest change to Example.hpp makes the warning disappear. One can eliminate for example derived class D5 or struct M or the second parameter of method toString().

Also setting BUILTIN_STL_SUPPORT to NO makes the warning go away.

On 2009-06-12 10:45:08 +0000, Peter Klotz wrote:

Created attachment 136411
A tar file containing everything to reproduce the problem

Contains Example.hpp/Example.cpp and a corresponding Doxyfile.

Running doxygen in the extraction directory produces the warning mentioned.

On 2009-06-13 12:22:44 +0000, Dimitri van Heesch wrote:

Confirmed. The problem should be fixed in the next subversion update.

On 2009-08-20 10:12:58 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.0. Please verify if this is indeed the case and reopen the
bug if you think it is not fixed (include any additional information that you
think can be relevant).

On 2009-08-22 21:17:04 +0000, Peter Klotz wrote:

The bug is indeed fixed in Doxygen 1.6.0.

Thanks a lot.

@doxygen doxygen closed this Jul 19, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.