Yes, though I'm not sure I'd recommend it over the other solutions posted: 
@statusoption = splice(@statusoption,
     (grep $statusoption[$_] eq $status, 0..$#statusoption)[0]);

[download]
Update: No need for splice when you just want a slice: 
@statusoption = @statusoption[
(grep {$status eq $statusoption[$_]} 0..$#statusoption)[0]
..$#statusoption];

[download]
Update: But splice is better than reassignment: 
splice(@statusoption, 0, (grep $status eq $statusoption[$_], 0..$#stat
+usoption)[0]);

[download]
Here's one that will short-circuit :-D: 
splice(@statusoption, 0,
   &{sub {
       grep {$status eq $statusoption[$_] and return $_} 0..$#statusop
+tion
    }}
);

[download]
Caution: Contents may have been coded under pressure.

In reply to Re: Grep question by Roy Johnson
in thread Grep question by hok_si_la

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.