comment on

Thanks for the SO-link ...

I totally agree with you that this naming is unfortunate.

To the point that I can't read my own modules w/o comments.

Now I'm pondering about aliasing them in my own modules, to help me understand my code

expanding the text from SO with potential aliases.

There are 2 sets of yes/no options. The function can be fatal (like die) or nonfatal (like warn). It can report just the line where the function was called, or it can report a full backtrace.

         Fatal  Backtrace      Alias
carp       N        N          warn_user °
cluck      N        Y          warn_full
croak      Y        N          die_user
confess    Y        Y          die_full
[download]

FWIW: Renaming subs is easy in Perl.

*warn_user = \&Carp::carp

Cheers Rolf
_{(addicted to the Perl Programming Language :)

Wikisyntax for the Monastery}

°) it's not warning the caller

In reply to Re^2: carp always showing stacktrace by LanX
in thread carp always showing stacktrace by LanX

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.


Problems? Is your data what you think it is?
	PerlMonks