You could avoid the filehandle headaches by keeping an array of references to Tie::File arrays. For example: - 
use strict;
use Tie::File;

my $nbdc_dir = '.';
my @nbdc_files = qw(1.txt 2.txt 3.txt);

my @nbdc_tied_files;
my @nbdc_data;
my $index=0;

foreach my $file (@nbdc_files) {
    tie my @tmparray, 'Tie::File', "./$nbdc_dir/$file" 
        or die "Can't open ./$nbdc_dir/$file";    
    push @nbdc_tied_files, \@tmparray;
    
    #get the first set of data values
    $nbdc_tied_files[0][0];
    $_ = $nbdc_tied_files[0][1];
    $nbdc_data[$index] = split(/\t/, $_);
    
    $index++;
 }

[download]
Update: Set $_ to value before split. Though I still don't understand what the reference to split output is for.

In reply to Re: Using a filehandle tucked into an array by bsdz
in thread Using a filehandle tucked into an array by redbeard

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.