Grammar Nazi version: 
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}{EFFECT} = 'UNDEF';
    }

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

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


__DATA__
// HEADER TAG
// VERSION TAG

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

TYPE VALUE2 EQUALS MAIN
I am useful test
ENDTYPE

TYPE VALUE3 EQUALS MAIN
CAUSE DEGRADED
ENDTYPE

TYPE VALUE4 EQUALS MAIN
EFFECT WARNING
ENDTYPE

[download]

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

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.