I frequently have to parse all kinds of output and every case is different, but I tend to go through the following process, each step makes the next one trivial, once you get the hang of it:

1) identify the lexical structure of the material -- can it be multiline, does indentation matter, etc.?

2) create a simple lexical analyser out of a hash of regexes and token names.

3) create a thrower or two that ejects white space and/or empty lines, comments etc.

4) create a trivial parser that calls the trivial lexer and thrower and has a subroutine to manage each type of opening landmark (encounter with an identifying string), typically loading it into a suitable structure or printing directly at the end of the section (via closing landmark)

5) if not printing as we go, traverse and print the structure

Update: code example of a lexer

package logparse;

sub new {
    return bless { LEX => { '\w+' => 'TOK_ID',
                            '^[:punct:]+' => 'TOK_PUNCT',
                            # and so on for all character classes you 
+identify
                 }};
}
 
sub lex { 
    my $self = shift;
    my $fh = $self -> { FH };
    $self -> { BUFFER } ||= <$fh> or goto EOF;
    PAT: while ( my ($pat, $tok) = each %{ $self -> { LEX }} ) {
        $/^($pat)(.*)$/ or next PAT;
        $self -> { BUFFER } = $2;
        $self -> { LEXVAL } = $1;
        return $tok;
    }

    $self -> { LEXVAL } = substr( $self -> { BUFFER }, 0, 1 );
    $self -> { BUFFER } =~ s/^.//;
    warn "unhandled content at $fh line $.\n";
    return '';

EOF: $self -> { LEXVAL } = '';
     return 'TOK_EOF';
}
[download]

1;

---

---

• 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.