|
Acme::JavaTrace - Module for using Java-like stack traces |
Acme::JavaTrace - Module for using Java-like stack traces
use Acme::JavaTrace;
warn "some kind of non-fatal exception occured";
die "some kind of fatal exception occured";
<buzzword>This module tries to improves the Perl programmer
experience by porting the Java paradigm to print stack traces, which
is more professional than Perl's way. </buzzword>
This is achieved by modifying the functions warn() and die()
in order to replace the standard messages by complete stack traces
that precisely indicates how and where the error or warning occurred.
Other than this, their use should stay unchanged, even when using
die() inside eval().
For a explanation of why I wrote this module, you can read the sildes of my lightning talk Entreprise Perl, available here: http://maddingue.org/conferences/yapc-eu-2004/entreprise-perl/
Here is an example of stack trace produced by Acme::JavaTrace
using a fictional Perl program:
Exception: event not implemented
at MyEvents::generic_event_handler(workshop/events.pl:26)
at MyEvents::__ANON__(workshop/events.pl:11)
at MyEvents::dispatch_event(workshop/events.pl:22)
at MyEvents::call_event(workshop/events.pl:17)
at main::(workshop/events.pl:30)
Please note that even the professionnal indentation present in Java traces is included in the trace.
Java, for its unhelpful kilometre-long stack traces.
Sébastien Aperghis-Tramoni <sebastien@aperghis.net>
Acme::JavaTrace is Copyright (C)2004 Sébastien Aperghis-Tramoni.
This program is free software. You can redistribute it and/or modify it under the same terms as Perl itself.
|
Acme::JavaTrace - Module for using Java-like stack traces |