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 are, as far as I have noticed, a fare share of questions that are of the: "I don't understand the difference between grep, map and foreach." written in paragraph form and peppered with keywords and/or small snippets of code. There is also the question of how do you parse out incorrect code/pseudo code.
I do think a short reminder above the poster's displayed previewed text is a decent idea worth exploring. Currently we have: "If something looked unlike you expected it to you might need to check out Writeup Formatting Tips" below the preview displayed post. Maybe that's not clear enough? If, as has been mentioned, the points are terse, few and clearly displayed above the preview, it could be helpful.
"...the adversities born of well-placed thoughts should be considered mercies rather than misfortunes." — Don Quixote
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||