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));
}
parse_line() should be called in list context, too.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|