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 734077 - no uniquely matching class member found for inline function definition where parameter argument names don't match
no uniquely matching class member found for inline function definition where ...
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.7
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2014-07-31 20:30 UTC by David Ritter
Modified: 2014-08-21 17:15 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Test case (3.51 KB, application/x-zip-compressed)
2014-07-31 20:30 UTC, David Ritter
Details

Description David Ritter 2014-07-31 20:30:45 UTC
Created attachment 282203 [details]
Test case

When an inline function is defined separate from the function body, doxygen will emit a warning that it can not match the class member for the inline function if the parameter names in the function definition do not match those in the function declaration.

Attached is the test case I developed in a ZIP file (with a contained Doxyfile).  There are 2 files in separate directories so that the following directory structure is created;

<root>
 |- Doxyfile
 |- include
    |- l
       |- test3.h
    |- m
       |- test.h

This directory structure was nessecary to reproduce the warning:

C:\Workspace\doxygen>doxygen
C:/Workspace/doxygen/include/m/test.h:23: warning: no uniquely matching class member found for
  template < T >
  int B< T >::col(int j)
Possible candidates:
  const int B< T >::col(int j) const' at line 11 of file C:/Workspace/doxygen/include/m/test.h
  int B< T >::col(int)' at line 16 of file C:/Workspace/doxygen/include/m/test.h
Comment 1 Dimitri van Heesch 2014-08-03 19:18:22 UTC
Confirmed. Should be fixed in the next GIT update.
Comment 2 Dimitri van Heesch 2014-08-21 17:15:19 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.8. 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).