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

typedef struct using same name hidden regardless of TYPEDEF_HIDES_STRUCT (Origin: bugzilla #606772) #3635

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

Comments

Projects
None yet
1 participant
@doxygen
Owner

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2010-01-12 20:00:26 +0000, Mark Courtney wrote:

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.

On 2010-01-12 20:02:55 +0000, Mark Courtney wrote:

Created attachment 151281
source file and doxyfile_*.cfg files to reproduce

On 2010-02-06 16:10:11 +0000, Dimitri van Heesch wrote:

*** Bug 608493 has been marked as a duplicate of this bug. ***

On 2010-02-06 16:12:05 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2010-02-21 12:57:35 +0000, Dimitri van Heesch wrote:

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.

@doxygen doxygen closed this Jul 2, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment