#!perl
use strict;
use warnings;
use Data::Dump 'pp';
##
my $inGeneDat = $ARGV[0] || "genes.dat";
open IN,'<',$inGeneDat or die "cannot open $inGeneDat\n";

{
  local $/ = '//';
  while ( my $record = <IN> ){
    my %values=();
    my @lines = split "\n",$record;
    for (@lines){
      if (/^(UNIQUE-ID|ACCESSION-\d|DBLINKS|COMMON-NAME) - (.*)/){
        my ($key,$val) = ($1,$2);
        # print "$key $val\n";
        if ($key eq 'DBLINKS'){ 
          if ($val =~ /ECOGENE \"(EG\d+)\"/){
            $values{$key} = $1;
          }
        } else {        
          $values{$key} = $val;
        }
      }
    };
    pp \%values; # build %HoNm as required

  }
}

close(IN);

[download]
poj

In reply to Re: file parsing by poj
in thread file parsing by AWallBuilder

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.