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 699437 - Trailing comments not rendered properly if MARKDOWN_SUPPORT enabled
Trailing comments not rendered properly if MARKDOWN_SUPPORT enabled
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.3.1
Other Windows
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
Depends on:
Blocks:
 
 
Reported: 2013-05-02 05:15 UTC by David Haney
Modified: 2013-05-19 12:35 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description David Haney 2013-05-02 05:15:32 UTC
This issue was originally reported on Stack Overflow (http://stackoverflow.com/questions/16326563/doxygen-documentation-after-members-malfunction-cause-formatting-as-code-fragm)

The following code is not rendered correctly with Doxygen 1.8.3.1 (it was with Doxygen 1.8.2):

/** Test struct definition */
typedef struct
{
    int member_1;  /**< Single-line detailed description */
    int member_2;  /**< Multi-line detailed description.  Blah
                        blah blah */
} TEST_S;

The first line of member_2's description is documented as a code fragment. If MARKDOWN_SUPPORT is disabled, moved to the following line, or moved before member_2 (and switched to a leading doxygen comment), the documentation is rendered correctly.
Comment 1 Dimitri van Heesch 2013-05-11 20:48:35 UTC
Confirmed. Should be fixed in the next subversion update.
Comment 2 Dimitri van Heesch 2013-05-19 12:35:49 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.4. 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.