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 707567 - Asterisks in comment wrongly displayed for @code
Asterisks in comment wrongly displayed for @code
Status: RESOLVED FIXED
Product: doxygen
Classification: Other
Component: general
1.8.5
Other Mac OS
: Normal normal
: ---
Assigned To: Dimitri van Heesch
Dimitri van Heesch
: 709479 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2013-09-05 13:50 UTC by Wu Yongwei
Modified: 2013-12-24 18:59 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Wu Yongwei 2013-09-05 13:50:35 UTC
For a code snippet like:

/**
 * Functor to delete objects pointed by a container of pointers.
 *
 * A typical usage might be like:
 * @code
 * list<Object*> l;
 * ...
 * for_each(l.begin(), l.end(), delete_object());
 * @endcode
 */
struct delete_object
{
    template <typename _Tp>
    void operator()(_Tp* pointer) const
    {
        delete pointer;
    }
};

Previously (at least up to 1.8.0) Doxygen was able to generate the correct HTML/LaTeX output like:

 list<Object*> l;
 ...
 for_each(l.begin(), l.end(), delete_object());

1.8.5 generates:

* list<Object*> l;
* ...
* for_each(l.begin(), l.end(), delete_object());
*
Comment 1 stefan.romberg 2013-09-05 14:07:04 UTC
I can confirm this.

See also this description: http://stackoverflow.com/questions/18569169/doxygen-each-line-in-code-listings-starts-with-an-asterisk
Comment 2 Dimitri van Heesch 2013-09-06 11:55:45 UTC
Confirmed. This is an unfortunate regression in 1.8.5.
Should be fixed in the next GIT update.
Comment 3 Dimitri van Heesch 2013-10-05 19:39:58 UTC
*** Bug 709479 has been marked as a duplicate of this bug. ***
Comment 4 Dimitri van Heesch 2013-10-05 19:41:21 UTC
Git commit that fixed this bug: https://github.com/doxygen/doxygen/commit/23f337e64b95d3fa08f32980c866669b190c872f
Comment 5 Dimitri van Heesch 2013-12-24 18:59:55 UTC
This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.6. 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 (preferrably in the form of a self-contained example).