Always check for success on system calls.
Always check for success on system calls.
Anything that can go wrong (that depends on Perl interacting with your system in some way, whether opening a file, making a database connection, executing a program via system or backticks, or the like) needs to be checked. If your program can't continue if it can't open its configuration file, die. If you have a reasonable set of defaults available, warn.
You would use Carp in places where you need to get the context of the error. carp <=> warn and croak <=> die, but they report more details, making debugging easier.
Update: confess gives you a full stack trace -- which functions were called, what arguments did they get. It's industrial strength.
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.