Not to be a "me too", but they are correct. What you get is about all you're going to get. Having recently had to do much error analysis and debugging of a recent project, I can honestly say, though, that Perl does give some good messages, in general. It's just the process of picking apart the code, and the data, to find the "loose thread". Though, the use of <STDOUT> and <STDERR> in Perl have been a major help in that respect. Printing out bits and pieces of data where you can see them will go far to help you realize where the warnings and errors are occuring.
-
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.
|
