Sure,

my @lines = <FILE>;
[download]

chomp( my @lines = <FILE> );

open(FILE, "filepath") || die "Can't open file";
@array = <FILE>;
close(FILE);
[download]

So that line 1 in your file will be in $array[0], line 2 in $array[1], etc.

Hope that helps.

One way is to use Tie::File.

test.pl:

use Tie::File;
use Data::Dumper;

my $self = tie @array, "Tie::File", "test.pl";
print Dumper(\@array);
[download]

open FILE, '<', $filename
  or die "Can't open $filename: $!\n";
my @lines = <FILE>;
close FILE
  or die "Can't close $filename: $!\n";
[download]

will fill @lines. See also the $/ variable.

This caught my eye.

Sorry for being pedant but we are opening files here, so - unless you mistype your file handle, - you can always close a filehandle. Or am I wrong?
So there is no benefit of dieing on close. If we do not need to reset $., we need not even close it.


Cheers,
PerlingTheUK

Sorry for being pedant but we are opening files here, so - unless you mistype your file handle, - you can always close a filehandle. Or am I wrong?

No need to apologize for being pedantic :-). I can't think of a situation where close would fail on a plain old file on a local filesystem; for that, it's just habit. But networked filesystems, sockets, pipes, and so on can mess up close; besides, Always Check System Call Return Values is a good habit to get into.

--
Yours in pedantry,
F o x t r o t U n i f o r m
"Anything you put in comments is not tested and easily goes out of date." -- tye