Oh, goodie, another chance to put in a plug for CGI::Debug! I think CGI::Debug should be a standard module. I won't go into all the details, suffice it to say that while developing CGI code, 'use CGI::Debug' at the top of the code will make it much easier to catch and fix bugs.
A lot of visitors to DALnet #perl have problems with code that runs fine locally or on their shell on the server, but dies when run by the server uid (permissions usually), but they can't get at the logs to find out why. A neat feature of CGI::Carp is the carpout subroutine. carpout takes an open FILEHANDLE and directs STDERR to it. Give carpout a FILEHANDLE opened on a file in a directory under your home and you have access to perl's errors and warnings output. This won't help you with server errors, but with proper error handling in your code, you'll usually have enough to go on.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|