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 606772 - typedef struct using same name hidden regardless of TYPEDEF_HIDES_STRUCT
typedef struct using same name hidden regardless of TYPEDEF_HIDES_STRUCT
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.6.2
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 608493 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2010-01-12 20:00 UTC by Mark Courtney
Modified: 2010-02-21 12:57 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
source file and doxyfile_*.cfg files to reproduce (53.16 KB, application/octet-stream)
2010-01-12 20:02 UTC, Mark Courtney 		Details

Description Mark Courtney 2010-01-12 20:00:26 UTC 
Given the following code:

typedef struct _diffName {} diffName;
typedef struct sameName {} sameName;

When TYPEDEF_HIDES_STRUCT is set to "YES", the generated Doxygen XML contains the following:
struct diffName
struct sameName

When TYPEDEF_HIDES_STRUCT is set to "NO", the generated Doxygen XML contains the following:
struct _diffName
struct sameName
typedef diffName

With TYPEDEF_HIDES_STRUCT set to "NO", I would also expect a "typedef sameName" to be included in the Doxygen XML.
Comment 1 Mark Courtney 2010-01-12 20:02:55 UTC 
Created attachment 151281 [details]
source file and doxyfile_*.cfg files to reproduce
Comment 2 Dimitri van Heesch 2010-02-06 16:10:11 UTC 
*** Bug 608493 has been marked as a duplicate of this bug. ***
Comment 3 Dimitri van Heesch 2010-02-06 16:12:05 UTC 
Confirmed. Should be fixed in the next subversion update.
Comment 4 Dimitri van Heesch 2010-02-21 12:57:35 UTC 
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.3. 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.