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

Regression: a struct ivar in ObjC class screws up method identification (Origin: bugzilla #582676) #3392

doxygen opened this Issue Jul 2, 2018 · 0 comments


None yet
1 participant

doxygen commented Jul 2, 2018

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

Original attachment names and IDs:

On 2009-05-14 21:22:13 +0000, Peter wrote:

This is a regression between 1.5.8 and 1.5.9. If I have an ObjC class like this:

@interface MyStructClass : NSObject {
struct {
unsigned int _used;
unsigned int _reserved;
} _s;
int _i;

  • (int)aMethod;

doxygen 1.5.8 will properly identify the aMethod method as a virtual function:

<member kind="function" virtualness="virtual">

In doxygen 1.5.9, it (and any other methods in the class) get identified as a protected variable:

<member kind="variable" protection="protected">

Removing the struct, gives correct results in both versions of doxygen.

On 2009-05-14 21:25:39 +0000, Peter wrote:

Created attachment 134670
File demonstrating error

On 2009-05-14 21:26:33 +0000, Peter wrote:

I've attached a tgz file containing my test header, DOXYGEN file, and the Tags files created by 1.5.8 and 1.5.9.

On 2009-05-17 12:27:47 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed again in the next subversion update.

On 2009-08-20 10:12:48 +0000, Dimitri van Heesch wrote:

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

@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