How about a hash with col* as keys and data_line* as an array stored for the corresponding key?
Well lets see what to do... 
my %database;
my $curCol;
for(<DATASET>)
{
  if(/^(col\d+)\s+(.*)/)  #(.+) isnt good but as I dont know exactlly 
+how your data looks like...
  {
    push(@{$database{$1}}, $2);
    $curCol = $1;
  }
  elsif(/^\s+(.*)/)
  {
    push(@{$database{$curCol}}, $1);
  }
}

[download]
Maybe I also expalin a little bit, but I didnt try out the code so there might be some bugs in it, I didnt notice. You create a hash of arrays with col as key and push each line that has no new col into the previous col. If there is a new col a new key and array is initiated and so on. I hope it is logical and helpfull.

In reply to Re: parsing a file by Anonymous Monk
in thread parsing a file by kulls

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.