comment on

A hash-of-hashes might help (perldsc):

use warnings;
use strict;

my %results;
my $type;
while (<DATA>) {
    next if m{^/};
    next unless /\S/;

    if (/^TYPE\s(\S+)/) {
        $type = $1;
        $results{$type}{CAUSE } = 'UNDEF';
        $results{$type}{AFFECT} = 'UNDEF';
    }

    if (/^(CAUSE|AFFECT)\s(\S+)/) {
        $results{$type}{$1} = $2;
    }
}

for (sort keys %results) {
    print "$_:$results{$_}{CAUSE},$results{$_}{AFFECT}\n";
}


__DATA__
// HEADER TAG
// VERSION TAG

TYPE VALUE1 EQUALS MAIN
I am useless text
CAUSE FAIL
AFFECT ERROR
ENDTYPE

TYPE VALUE2 EQUALS MAIN
I am useful test
ENDTYPE

TYPE VALUE3 EQUALS MAIN
CAUSE DEGRADED
ENDTYPE

TYPE VALUE4 EQUALS MAIN
AFFECT WARNING
ENDTYPE
[download]

prints:

VALUE1:FAIL,ERROR
VALUE2:UNDEF,UNDEF
VALUE3:DEGRADED,UNDEF
VALUE4:UNDEF,WARNING
[download]

In reply to Re: File Parsing and Pattern Matching by toolic
in thread File Parsing and Pattern Matching by Mark.Allan

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.


laziness, impatience, and hubris
	PerlMonks