Yet another brief addition: the message $! tells you the
cause of the addition, but not the source.
Zaxo already
told you that leaving that newline out makes
die tell
the terminal which line of code generated that error.
However, that's not immediately informative. The command
probably interpretets a variable to generate the syscall,
so in general it's a good idea to provide that information :
open( INPUT, $filename ) or die "Could not open $filename: $!";
# or
rename( $old, $new ) or die "Could not rename $old to $new: $!";
As a third step, you can use Carp to print out the chain
of callers. This is useful when your code
is distributed over more than one file.
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.