Parsing is extremely fragile?

[adamdahan]

I have a little snippet for you to test and I am curious to know if you have any insights about why the parsing breaks down so easily before I go in and try to fix it up.

This markdown below should render a simple while loop

        ``\nwhile (YES) {\n    printf(\"Help, I am stuck in an infinite loop!\\n\");\n}\n``

But it does not render using your parser. Interestingly enough though this does:

       `` while (YES) { \n printf(\"Help, I am stuck in an infinite loop! \\n\"); } ``

I found that the initial newline and the last two newline chars are breaking it.

Any ideas?

[Coeur]

Hello @adamdahan, and thanks for raising the issue.

I built the regex myself in an attempt to be compatible with Character Escaping. See #46 for what was the problem, and 437d9a9#diff-842045870396c3236b1fad63acfe6264R140 for the solution (@"(?<!\\\\)(?:\\\\\\\\)*+(+)(.*?[^].*?)(\\1)(?!)"`).

In branch 3.x, the regex is the same, but written @"(?<!\\\\)(?:\\\\\\\\)*+" concatenated with @"(%@+)(.*?[^%@].*?)(\\1)(?!%@)" where %@ is replaced with ```.

I'll look into the issue, but feel free to provide a pull request to master.

[Coeur]

Maybe changing options:(NSRegularExpressionOptions)0 to options:NSRegularExpressionDotMatchesLineSeparators is enough.