Return to Question

• Markdown to HTML which is a blob of regexps
• Markdown to HTML, again which has an... interesting (confusing) split/map nesting (and didn't work with XHTML)

• Markdown to HTML which is a blob of regexps
• Markdown to HTML, again which has an... interesting (confusing) split/map nesting (and didn't work with XHTML)

tags contains simple tags, which have equivalent start and end markdown sequences and cannot be nested within themselves, while stags contains special tags which have different start and end tags. When looking for tags, it goes through a loop testing to see if substrings of each length match, which looks messy.

tags contains simple tags, which have equivalent start and end markdown sequences and cannot be nested within themselves, while stags contains special tags which have different start and end tags. When looking for tags, it goes thru a loop testing to see if substrings of each length match, which looks messy.

• replaceAll() is used everywhere on my app, so it's not going to change, and I don't think fiddling with String.prototype is wrong.
• html() does an HTML escape. It doesn't escape everything and doesn't work for all cases, but I'm happy enough.
• warning() is just a function that collections whatever complaints inlineMarkdown has. This is just a console.log for testing, but I display the warnings to the user when using it client-side.
• spanMarkdown() deals with linkifying and simple inline-markdown things that can be done with regex – it's easy to add stuff like oneboxing here.
• inlineMarkdown() parses teh markdownz! (and depends on the other functions)

tags contains simple tags, which have equivalent start and end markdown sequences and cannot be nested within themselves, while stags contains special tags which have different start and end tags. When looking for tags, it goes thru a loop testing to see if substrings of each length match, which looks messy.

• replaceAll() is used everywhere on my app, so it's not going to change, and I don't think fiddling with String.prototype is wrong.
• html() does an HTML escape. It doesn't escape everything and doesn't work for all cases, but I'm happy enough.
• warning() is just a function that collections whatever complaints inlineMarkdown has. This is just a console.log for testing, but I display the warnings to the user when using it client-side.
• spanMarkdown() deals with linkifying and simple inline-markdown things that can be done with regex – it's easy to add stuff like oneboxing here.
• inlineMarkdown() parses teh markdownz! (and depends on the other functions)

tags contains simple tags, which have equivalent start and end markdown sequences and cannot be nested within themselves, while stags contains special tags which have different start and end tags. When looking for tags, it goes through a loop testing to see if substrings of each length match, which looks messy.