It's not that hard. The process basically is:

my %info; # here we collect all information

# The name and order of the columns we want to print
my @columns = qw(qw(gi version cds);

sub flush_info {
    # print out all information:
    print join '*', @info{@columns};

    # and forget the collected information
    %info = ();
};

while (<>) {
    if (m!GI:(\d+)!) {
        if ($info{cds}) { # we are in a CDS block
            $info{gi} = $1;
        };
    } elsif (m!^\s+CDS\s+(.*)!) {
        # a new gene information has started
        flush_info();

        # now remember the CDS
        $info{cds} = $1
    } elsif (m!^VERSION.*\w:(\d+)! ) {
        $info{ version } = $1;
    } else {
        warn "Ignoring unknown line [$_]\n";
    };
};

# Output any leftover information:
flush_info();

[download]

In reply to Re^7: Read, match string and print by Corion
in thread Read, match string and print by sophix

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.