I'd suggest a different call sequence for "yoink()":
yoink( \@arr, $var ); # pass an array ref and a scalar
The sub definition could go something like this, if you
don't mind making a copy of the array in order to do the
work:
sub yoink
{
my ($arr_ref, $kill_pattern) = @_;
my @out_arr;
for (@$arr_ref) {
push @out_arr, $_ unless (/^$kill_pattern$/)
}
@$arr_ref = @out_arr;
}
The "yoink" could also use the "splice" function (see perldoc
-f splice) to edit the array in place; I suspect the "optimal"
choice would depend on array size and number of elements being
removed -- with big arrays, doing just a few edits will go
best with
splice, but doing lots of edits might go quicker using selective copying to a
separate array. (For small arrays, there
won't be a noticeable difference.)
update: IO's solution is better than mine,
of course. (I just forgot that I should've known better...)
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, 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, 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.
|
|