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.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||