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

No space between * and tag (e.g. \endcode) makes parser misbehave (Origin: bugzilla #571561) #3272

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 minor in component general for ---
Reported in version 1.8.2-SVN on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2009-02-12 22:57:21 +0000, Mike Youell wrote:

Please describe the problem:
If there is no space between the *'s and a tag (e.g. \endcode) then the parser doesn't behave correctly (i.e. it displays an extra start in the documented code block).

/**

  • Example usage:
    *\code
  • $bf = new CCryptBlowfish('some secret key!');
  • $encrypted = $bf->Encrypt('this is some example plain text');
  • $plaintext = $bf->Decrypt($encrypted);
  • echo "plain text: $plaintext";
    *\endcode
    */

Steps to reproduce:

/**

  • Example usage:
    *\code
  • $bf = new CCryptBlowfish('some secret key!');
  • $encrypted = $bf->Encrypt('this is some example plain text');
  • $plaintext = $bf->Decrypt($encrypted);
  • echo "plain text: $plaintext";
    *\endcode
    */

The above code produces an extra "*" at the end of the documented code.

This code is ok:

/**

  • Example usage:
  • \code
  • $bf = new CCryptBlowfish('some secret key!');
  • $encrypted = $bf->Encrypt('this is some example plain text');
  • $plaintext = $bf->Decrypt($encrypted);
  • echo "plain text: $plaintext";
  • \endcode
    */

Actual results:
You see an extra start "*" in the documented code block.

Expected results:
No extra star.

Does this happen every time?
yes

Other information:

On 2012-11-18 11:07:16 +0000, Dimitri van Heesch wrote:

Changed version 'latest' to '1.8.2-SVN' so I can remove 'latest' as an option as it is a moving target.

On 2013-01-27 17:52:33 +0000, albert wrote:

Created attachment 234556
PATCH: fix proble with asterisk without space following it

This patch fixes the problem as indicated in the bug report as well as other problems where directly after an asterisk there is no space.

On 2013-02-23 10:06:45 +0000, Dimitri van Heesch wrote:

Thanks, I'll include the patch in the next subversion update.

On 2013-05-19 12:35:48 +0000, Dimitri van Heesch wrote:

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.

@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