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 576533 - C: enum pointer in struct completely missing from documentation
C: enum pointer in struct completely missing from documentation
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: build
1.5.8-SVN
Other Linux
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2009-03-24 09:04 UTC by Bart van Deenen
Modified: 2010-10-09 08:19 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bart van Deenen 2009-03-24 09:04:29 UTC
I did these tests on Linux, with doxygen compiled from svn (684)
file test.c

/*! my spectacular enum */
enum E {
    one, //!< I
    two, //!< II
};

/*! my spectacular struct */
struct S {
    int  *i; //!< integer doc
    enum E  e; //!< enum doc
    enum E  *ep; //!< enum pointer doc
};

void main()
{
}


Doxyfile modifications 
OPTIMIZE_OUTPUT_FOR_C  = YES
EXTRACT_ALL            = YES
INPUT                  = test.c


In the generated S Struct Reference page the 'ep' field is absent.

If there's anything I can do to help resolve this issue, please let me know.

Thanks for the wonderful tool anyway.

Bart
Comment 1 Dimitri van Heesch 2010-06-22 20:13:49 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2010-06-25 11:49:03 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.1. 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.
Comment 3 Dimitri van Heesch 2010-10-09 08:19:46 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.7.2. 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.