IMO There is a big advantage to the first style however: it actually defines the subs in such a way that you don't get weird error messages about stuff happening in an anon sub. Likewise you can set breakpoints in the debugger and stuff with the former but with the latter its not so easy. There are ways around this, but they aren't straight-forward.
use Carp qw(confess);
local *foo=sub { confess "What the fook!" };
eval qq[sub bar { confess "What the wook!" } 1 ]
or die "failed to eval code: $@";
eval {
foo(); 1
} or print $@;
eval {
bar(); 1
} or print $@;
__END__
What the fook! at c:\temp\die.pl line 3
main::__ANON__() called at c:\temp\die.pl line 9
eval {...} called at c:\temp\die.pl line 8
What the wook! at (eval 1) line 1
main::bar() called at c:\temp\die.pl line 13
eval {...} called at c:\temp\die.pl line 12
---
$world=~s/war/peace/g
-
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.
|