After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 585543 - Matching of declaration and definition fails
Matching of declaration and definition fails
Status: VERIFIED FIXED
Product: doxygen
Classification: Other
Component: general
1.5.9
Other All
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-06-12 10:42 UTC by Peter Klotz
Modified: 2009-08-22 21:17 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
A tar file containing everything to reproduce the problem (18.00 KB, application/x-gzip)
2009-06-12 10:45 UTC, Peter Klotz
Details

Description Peter Klotz 2009-06-12 10:42:24 UTC
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.
Comment 1 Peter Klotz 2009-06-12 10:45:08 UTC
Created attachment 136411 [details]
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.
Comment 2 Dimitri van Heesch 2009-06-13 12:22:44 UTC
Confirmed. The problem should be fixed in the next subversion update.
Comment 3 Dimitri van Heesch 2009-08-20 10:12:58 UTC
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).
Comment 4 Peter Klotz 2009-08-22 21:17:04 UTC
The bug is indeed fixed in Doxygen 1.6.0.

Thanks a lot.