Skip to content
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

Double underscore in identifiers not ignored by markdown (PATCH) (Origin: bugzilla #688463) #4955

Closed
doxygen opened this Issue Jul 2, 2018 · 0 comments

Comments

Projects
None yet
1 participant
@doxygen
Copy link
Owner

doxygen commented Jul 2, 2018

status RESOLVED severity normal in component general for ---
Reported in version 1.8.2 on platform Other
Assigned to: Dimitri van Heesch

Original attachment names and IDs:

On 2012-11-16 13:52:37 +0000, René Papenhoven wrote:

A reference to the following identifier is not correctly processed by markdown.

MyNameSpace::__MyClass::__MyMethod()

The problems is that the function findEmphasisChar() in markdown.cpp only checks correctly for a single character emphasis token to end the emphasis part.

In my opinion it should check for a emphasis token of the same size as the start token.

I've modified this function in the attached file (based on svn revision 833) by adding a parameter to indicate the size of the token.

On 2012-11-17 09:33:15 +0000, Dimitri van Heesch wrote:

Did you forget to attach the file?

On 2012-11-17 11:14:12 +0000, René Papenhoven wrote:

Created attachment 229225
Modified markdown.cpp for emphasis fix

2nd attempt for attachment. (1st somehow failed)

On 2012-11-17 16:34:53 +0000, Dimitri van Heesch wrote:

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

On 2012-12-26 16:09:30 +0000, Dimitri van Heesch wrote:

This bug was previously marked ASSIGNED, which means it should be fixed in
doxygen version 1.8.3. 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
You can’t perform that action at this time.