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

Asterisks in comment wrongly displayed for @code (Origin: bugzilla #707567) #5288

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

On 2013-09-05 13:50:35 +0000, Wu Yongwei wrote:

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
    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());

On 2013-09-05 14:07:04 +0000, stefan.romberg@informatik.uni-augsburg.de wrote:

I can confirm this.

See also this description: http://stackoverflow.com/questions/18569169/doxygen-each-line-in-code-listings-starts-with-an-asterisk

On 2013-09-06 11:55:45 +0000, Dimitri van Heesch wrote:

Confirmed. This is an unfortunate regression in 1.8.5.
Should be fixed in the next GIT update.

On 2013-10-05 19:39:58 +0000, Dimitri van Heesch wrote:

*** Bug 709479 has been marked as a duplicate of this bug. ***

On 2013-10-05 19:41:21 +0000, Dimitri van Heesch wrote:

Git commit that fixed this bug: SHA: 23f337e

On 2013-12-24 18:59:55 +0000, Dimitri van Heesch wrote:

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

@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