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

Empty class definitions not included in Tokens file (Origin: bugzilla #557035) #3136

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.5.7.1 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2008-10-20 05:53:50 +0000, Peter wrote:

Please describe the problem:
Doxygen expects a class to always have a member symbol (and to start with a +/-). If the class has no members, doxygen fails to detect the class. Running doxygen over this header file with EXTRACT_ALL=YES causes no symbols to be found:

#import <Foundation/Foundation.h>

@interface MyEmptyClass : NSObject
@EnD

Steps to reproduce:

Actual results:

Expected results:

Does this happen every time?

Other information:

On 2008-10-21 18:09:47 +0000, Dimitri van Heesch wrote:

I couldn't reproduce this (e.g. for me doxygen does produce a MyEmptyClass).
Can you attach a self-contained example (source+config file in a zip) that allows me to reproduce the problem?

On 2008-10-21 19:41:56 +0000, Peter wrote:

You're right. The HTML pages do get generated in this case. I was building the docset files and looking at the Tokens.xml file, which does not list MyEmptyClass. I've updated the bug summary and will attach my test files.

On 2008-10-21 19:44:29 +0000, Peter wrote:

Created attachment 121055
Sample header and config showing an empty class not listed in Tokens.xml

On 2009-10-24 18:56:44 +0000, Dimitri van Heesch wrote:

Confirmed. Should be fixed in the next subversion update.

On 2009-12-30 13:38:54 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.6.2. 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