Thanks everyone for the responses, and especially thanks for the examples using the various parsing modules. I now have those to refer to in the future.

I've settled on a simplified version of my original code, incorporating the suggestions from [id://grandfather], as follows:
#!/usr/bin/perl -w use strict; my $datafile = "stuff.csv"; my @fields; my $data; open DATA, "<$datafile" or die "Could not open $datafile:$!\n"; # Grab the first (header) line, discarding the first two fields $_ = <DATA> or die "Empty file"; chomp((undef, undef, @fields) = (split /\t/)); # Grab the rest, and populate the hashref while (<DATA>) { chomp(); my ($user, @userdata) = (split /\t/); $data->{$user}{$_} = shift @userdata for (@fields); } close DATA;
This is much "nicer" than my original, and I'm now a happy vegemite :)

--Darren

In reply to Re: Parsing CSV into a hash by McDarren
in thread Parsing CSV into a hash by McDarren

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.