Its worse then that... your tests do the same amount of abuse. Have you considered doing this with a closure?
sub getAnyAll
{
my $code = shift;
my $Any = sub {
my @A = @{$_[0]}; # I like to dereference early, it makes
my @B = @{$_[1]}; # the rest of the code more readable.
while( @A and @B )
{
return 1 if &$code( pop(@A), pop(@B) )
}
return 0
};
my $All = sub {
my @A = @{$_[0]};
my @B = @{$_[1]};
while( @A and @B )
{
return 0 unless &$code( pop(@A), pop(@B) )
}
return 1
};
return ( $Any, $All );
}
that's untested, but gives you the idea. By the way...
poping arrays passed by reference might not be such a good idea either...
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.