NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.
All the Perl that's Practical to Extract and Report
use Perl Log In
hanekomu (8123)
hanekomu
(email not shown publicly)
http://hanekomu.at/blog/
AOL IM: hanekomu (Add Buddy, Send Message)
Go (Baduk) player and Perl hacker.
(email not shown publicly)
http://hanekomu.at/blog/
AOL IM: hanekomu (Add Buddy, Send Message)
Go (Baduk) player and Perl hacker.
Saturday November 10, 2007
05:59 AM
Carp::Source
I've released Carp::Source. It exports a function, source_cluck(), that does pretty much the same as Carp's cluck() except it also displays the source code context of all call frames, with three lines before and after each call being shown, and the call being highlighted. Enjoy.
Carp::Source
More |
Login
| Reply
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
about I/O disciplines and I should retire to the Tassili-in-Aijer
mountains in Sahara as a camel herder :-)
-- Jarkko Hietaniemi
Stories, comments, journals, and other submissions on use Perl; are Copyright 1998-2006, their respective owners.
Not very useful to me in this form (Score:1)
In general I find that I don’t want to decide at the time of writing the code whether a particular instance of
croakwill dump a stack trace or not. All I can decide is whether to throw an exception or warning in the current context or that of the caller, depending on what makes more sense. Whether to get stack traces or not is something I can only decide when I’m running the code: while investigating a problem, I often want to turn them on globally.So I love Carp::Always, which makes all
warnRe: (Score:1)
Quick turnaround [cpan.org]!
Devel::file similar module (Score:1)