PPI is in no way robust enough for this use case. Source filters will never be appropriate for production use.
use strict;
use warnings;
use experimental 'signatures';
use Nice::Try;
sub foo { 1 }
try {
my $k = sub ($f = foo()) {};
}
catch ($e) {
warn "caught: $e";
}
__END__
Global symbol "$e" requires explicit package name (did you forget to d
+eclare "my $e"?) at bad-syntax.pl line 10.
syntax error at bad-syntax.pl line 10, near ") {"
Execution of bad-syntax.pl aborted due to compilation errors.
The module has other serious issues:
use strict;
use warnings;
use Nice::Try;
{
package MyException;
use overload '""' => 'message';
sub message { $_[0]->{message} }
sub new { my $class = shift; bless { @_ }, $class }
sub throw { my $class = shift; die $class->new(message => shift) }
}
try {
MyException->throw("hi\n");
}
catch (MyException $e) {
warn "working catch: $e";
}
catch ($e) {
warn "broken catch: $e";
}
__END__
$ perl bad-exception.pl
broken catch: hi at bad-exception.pl line 21.
-
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.
|