Two entries for a single member in Doxygen XML (Origin: bugzilla #732594)

[doxygen]

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

Original attachment names and IDs:

• test.zip (ID 279788)
• class_a.xml (ID 279789)

On 2014-07-01 23:09:11 +0000, victor.zverovich@gmail.com wrote:

Consider the following example:

template
class A {
typedef T U;
U f();
};

template
typename A::U A::f() {}

The XML generated with Doxygen 1.8.6 contains two entries for the member function template f:

  <member refid="class_a_1a1534227ab314f4f20f53729ced034ffd" prot="private" virt="non-virtual"><scope>A</scope><name>f</name></member>
  <member refid="class_a_1aa592f5abbcd7a8d3ad8345a0e538715d" prot="public" virt="non-virtual"><scope>A</scope><name>f</name></member>

Moreover, one of these entries have prot=public. When generating an HTML file only a single member is shown, but it is incorrectly placed in the Public Member Functions section.

On 2014-07-02 08:07:04 +0000, albert wrote:

I tried to reproduce the problem with the 1.8.6 version by copying the given example lines into a file (aa.h) and I could not find the referenced text, I found:

Af
AU

This looks OK to me.

Please add a (small) self-contained example (source+results+config file in a zip or tar) to reproduce / showing the problem.

On 2014-07-02 16:06:39 +0000, victor.zverovich@gmail.com wrote:

Created attachment 279788
example

On 2014-07-02 16:08:16 +0000, victor.zverovich@gmail.com wrote:

Created attachment 279789
output

On 2014-07-02 16:09:38 +0000, victor.zverovich@gmail.com wrote:

I've added a self-contained example and the generated XML output. Please let me know if you need any additional information.

On 2014-08-08 12:03:18 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next GIT update.

On 2014-08-21 17:15:21 +0000, Dimitri van Heesch wrote:

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).