20. Expect the worst - don't always think that the user's input will be nice, clean, and tidy.
21. Always use die
(sometimes) if the code has a possibility of failing.
22. DO NOT try to reinvent CGI
.pm. It is already good enough as is and should not try to be re-written. Check out chromatic
's homenode and generally(.*?) just look at daily posts on why not to.
I just thought I should point that out.
Almost a Perl hacker.
Dave AKA damian
I encourage you to email me
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||