Is there any reason that the following structure would be inappropriate?
#!/usr/bin/perl -w use strict; use Text::CSV_XS; my $fh; unless (open $fh, "filename") { die "No file available\n"; } my $csv = Text::CSV_XS->new({binary => 1}); my @people; <$fh>; # Drop column names on the floor while ( my $line = <$fh> ) { my $status = $csv->parse($line); my @columns = $csv->fields(); my %h; @h{('Name','Comment')} = @columns; push @people, \%h; } close $fh; print "Name: " . $people[2]->{'Name'} . ", Comment: " . $people[2]->{'Comment'} . "\n";

It seems to me that keeping the associated data together is a better solution to this problem. Also, looping by key field is more flexible than looping by dedicated array name.


In reply to Re: Read the csv file to a hash.... by snopal
in thread Read the csv file to a hash.... by isha

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.