Sure, grep will simplify that, with a minor change in behavior - maybe for the better.

sub lsearch { my $item = shift; grep { $item eq $_[$_] } 0 .. $#_; }
That will return the empty list for false, and otherwise a list of each index that succeeds

Usage becomes, for your example,

for (reverse lsearch $item, @list) { splice @list, $_, 1 } # or splice @list, $_, 1 for reverse lsearch $item, @list;
so all instances of $item are removed from the array. The reverse call is needed to preserve the indexes from being shifted out of sync by splice.

An alternative is to define a winnow() function to do it all:

sub winnow { my $item = shift; grep { not $item eq $_ } @_; } @list = winnow $item, @list;
That is maybe less flexible, but I think cleaner.

After Compline,
Zaxo


In reply to Re: lsearch for perl? by Zaxo
in thread lsearch for perl? by matt.tovey

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • 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:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.