filehandles

[sivasish]

i am getting an error when i am trying to compile folling program in
perl

#!/usr/bin/perl-w
$file= 'siva.pep';
open(FILENAME,$file);
@protein=<FILENAME>;
print @protein;
close FILENAME;

ERROR - readline<>is a closed filehandle FILENAME.........

file "siva.pep" is stored in F DIRECTORY.
I am not able understand the error. .

 

[Justin C]

i am getting an error when i am trying to compile folling program in
perl

#!/usr/bin/perl-w
$file= 'siva.pep';
open(FILENAME,$file);
@protein=<FILENAME>;
print @protein;
close FILENAME;

ERROR - readline<>is a closed filehandle FILENAME.........

Just because you said open siva.pep doesn't mean siva.pep got opened.

open(FILENAME,$file) or die "Cannot open FILENAME: $!"

would give you a clue.

"perldoc -f open" for better was to use that function.


Justin.

 

[Brian McCauley]

i am getting an error when i am trying to compile folling program in
perl

In addition to the other useful advice you've been given it appears
that you have jumped to a conclusion that that this is a compile time
error, and this may have coloured your attempts to understand it.

 

[Matt Garrish]

Just because you said open siva.pep doesn't mean siva.pep got opened.

open(FILENAME,$file) or die "Cannot open FILENAME: $!"

would give you a clue.

"perldoc -f open" for better was to use that function.

Actually, the open command information is a bit too general in scope.
Although it makes reference to the three-argument form (which what I'm
assuming you mean by better ways), as a description of of all the ways
to use open it doesn't push any one method, and certainly not using
scalars over barewords. I thought perlopentut made reference to the
benefits of using the syntax:

open (my $infile, '<', $file) or die "Cannot open $infile : $!";

but even it is lacking. Since it's generally accepted in current
practice that this is the way one should be opening files, shouldn't
the documentation be updated to refllect this fact, or am I missing the
discussion somewhere?

Matt