I think this <code></code> and <p></p> parser would be harder to implement than it seems (even keeping in mind your counter points). [...] There is also the question of how do you parse out incorrect code/pseudo code.
Does that parser have to be complete and perfect? All we want at this point is a simple check that the raw posting text contains one or more <p> and zero or more <code> or <c> tags. (Tags, not elements. We don't even have to check for the closing tags. Existing code handles missing or mis-placed tags quite well.) Unless that condition is met, the poster will see a hint that (s)he should check is posting. Implementing those checks could be done using one or two simple regexps.
Today I will gladly share my knowledge and experience, for there are no sweeter words than "I told you so". ;-)
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||