Comments on C for Coding: Markdown, Block Parsing and the Road to Hell

@StoneCypher: did I? Not that I can see. What are ...

2010-02-03T12:53:53.864+08:00

@StoneCypher: did I? Not that I can see. What are you referring to?

Did you just claim that Java invented the sealed c...

2010-02-03T12:51:53.362+08:00

Did you just claim that Java invented the sealed class concept?

@Evan: your supposition regarding resultant markup...

2010-02-02T15:06:19.694+08:00

@Evan: your supposition regarding resultant markup is correct. But, like I said, I'll probably code a special case for the previous behaviour at least as an option.

Regarding block-level tags, my code is actually far less strict about their placement and this is the exception to the block-then-inline rule I referred to earlier: the inline parse may find block level tags.

I'm also planning to go further and turn markup into markdown where applicable.

I'm not sure you can drop the case of list items w...

2010-02-02T14:47:22.049+08:00

I'm not sure you can drop the case of list items with paragraphs. For one, I've always liked a bit more space around my bullet points which this gives you an easy way to do. For another, if you do the following markdown will create HTML with some funky spacing:

- One

- Two

 Too

- Three

- Four

If I understand your rules correctly, with your parser this will produce the following HTML:

<ul>
 <li>one</li>
 <li>
 two
 too
 </li>
 <li>three</li>
 <li>four</li>
</ul>

Whereas the current parser produces:

<ul>
 <li>one</li>
 <li>
 two
 too
 </li>
 <li>three</li>
 <li>four</li>
</ul>

Which looks a lot better.

P.S. You didn't mention block level HTML tags, which "must be separated from surrounding content by blank lines, and the start and end tags of the block should not be indented with tabs or spaces". That's being handled okay?