multifoo sub { $_ * 2}, sub { foo ($_) }, @things;
hoopsy hoops, right?
And now the method body:
sub onefoo {
my ($reasonably_named_sub, @params) = @_;
whatever;
for my $foo (tweaked @params) {
$reasonably_named_sub->($foo);
}
}
sub multifoo {
my ($toDo, $filter, @params) = @_;
whatever;
for my $foo (grep $filter->(), tweaked @params) {
$toDo->($foo);
}
}
Yieieiaield anyone?
There is a little syntactic sugar for functions (not methods) in Perl, but the difference between using the sugar and not is tiny. If I need to pass two "pieces of code" into my subroutine, I pass them, I name them and I call them the same way I would if I had just one.
In Ruby, if your method gets a single block/closure parameter, you do not get to name the parameter, you use the ill-named statement yield and it kinda, behind the scenes, maybe, works. If you need to pass two you are, basically, screwed. But then 640KB ought to be ... I mean one block ought to be enough for anybody.
Jenda
Enoch was right!
Enjoy the last years of Rome.
-
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.