(I think) There's no real reason why the values shouldn't be passed in via @_ in the normal way.
sub test (&@) {
my $code=shift;
map $code->( $_, 'other', 'params' ), @_;
};
test { print "\$_ = $_ \@_ = '@_'"; } 1 .. 10;
$_ = 1 @_ = '1 other params'
$_ = 2 @_ = '2 other params'
$_ = 3 @_ = '3 other params'
$_ = 4 @_ = '4 other params'
$_ = 5 @_ = '5 other params'
$_ = 6 @_ = '6 other params'
$_ = 7 @_ = '7 other params'
$_ = 8 @_ = '8 other params'
$_ = 9 @_ = '9 other params'
$_ = 10 @_ = '10 other params'
(I think) The same could be done for File::Find and other subs that take anon. blocks/subs as args--sort blocks, List::Util functions etc.
Examine what is said, not who speaks.
"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon
-
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.
|