Your data lines are different enough that each type needs its own parser. A hash of coderefs ("dispatch table") will do that nicely, 

my $parser = {
    OFF => sub {()},
    SUCCESS => sub {
        local $_ = shift;
        /\((\w*)\)/
    },  # call these in list context!
    ERROR1 => sub {
        local $_ = shift;
        /disk number \((\d+)\) at \((\d+:\d+)\)/;
    },
    WARNING1 => sub {
        local $_ = shift;
        /(\w.*)^/;
    }
};

sub parse_line {
    local $_ = shift;
    my ($key, $data) = split ':', $_, 2;
    $key =~ tr/()//d;
    ($key, $parser->{$key}->($data));
}

[download]
parse_line() should be called in list context, too.

After Compline,
Zaxo

In reply to Re: String parsing by Zaxo
in thread String parsing by hotshot

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.