A lot of monks here strongly recommend the use of -w (however, the use warnings pragma should now be used) and use strict.

Something I think that most people haven't touched on is the usefulness of the CGI::Carp module.

When you've been writing a CGI script, how many times has it run from the shell fine, only to give you the dreaded '500 Internal Server Error'. CGI::Carp writes a $SIG{__DIE__} handler so that die() calls are handled fine, and you get the same sort of error message in your browser that you would when running your script from the shell.

So, make sure you: 

use CGI::Carp qw(fatalsToBrowser)

[download]
in all your CGI scripts. It has saved me literally HOURS of debugging time.

In reply to CGI::Carp by SuperCruncher
in thread Reviews Quest by vroom

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.