I should point out that my comment followed arturo's
description of some horrible code. There've been
a few nodes discussing how horrible things can be
(I'm too lazy to look up more than one
link),
but it's probably nicer to try to explain why things
are horrible and clean them up (as in Ovid's CGI tutorial
spec, and arturo's suggestion). I was actually just
commenting on how much fun it is to be cruel sometimes.
But then arturo suggested making it nice instead of
mean. I do like looking at code and reading why it
is bad and how it can be improved,
I'm not sure I'm completely convinced it warrants its
own section...we've got quite a few sections
and there could be some confusion. And there's also
the question of if anyone wants to correct code that
the poster already knows is horrible (I assume anyone
whose own code is having problems will post to SoPW).
So I'd like to see posts like that, but I don't know
that they need a section.
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:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, 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, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.