I've sometimes used Carp, but in general found that I didn't really need the more extensive output
carp and croak don't make the output more extensive; they just report the caller to be the source of the error instead of the line where the error was found.
$ perl -Mlib=. -MMod -e'Mod::foo();'
Insufficient arguments at Mod.pm line 5. # carp
Insufficient arguments at -e line 1. # warn
They also have the advantage of being able to produce a full stacktrace on demand (e.g. PERL5OPT=-MCarp::Always). ...Oops, that also works for warn and die.
$ PERL5OPT=-MCarp::Always perl -Mlib=. -MMod -e'Mod::foo();'
Insufficient arguments at Mod.pm line 5.
Mod::foo() called at -e line 1
Insufficient arguments at Mod.pm line 6.
Mod::foo() called at Mod.pm line 6.
Mod::foo() called at -e line 1
-
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.
|