mkmcconn has asked for the wisdom of the Perl Monks concerning the following question:
Brethren,
In a learning experiment using multiple filehandles in a hash, I stumbled on something that I don't understand.
# the following (incorrect) line closes the filehandles#/usr/bin/perl -w use strict; local (*E,*F,*G); my $string = <<JUNK; I will print unless I perish JUNK my %rh = (E=> *E, F=> *F, G=> *G); open $rh{$_}, ">test_$_.txt" or die $! for keys %rh; print { $rh{$_}} $_.$string for keys %rh;
close $_ or die $! for keys %rh; # so that this (correct) line dies
close $rh{$_} or die $! for keys %rh; #error: # Bad file descriptor at C:\Perl\scripts\test5.pl line 20.
Note that strict is being used.
Why is $_, above, allowed to be used as a Filehandle? In the other contexts, open() or print (), the script would have failed with appropriate messages that 'String ('F') can't be used ..' etc.
So, close() doesn't expect the same strictness that open() does. Is that as it ought to be?
(ActiveState perl 5.6.1)
mkmcconn
|
---|
Replies are listed 'Best First'. | |
---|---|
Re: unexpected close() success on (non-) filehandle
by tachyon (Chancellor) on Nov 21, 2001 at 18:33 UTC | |
(tye)Re: unexpected close() success on (non-) filehandle
by tye (Sage) on Nov 21, 2001 at 22:24 UTC | |
by mkmcconn (Chaplain) on Nov 21, 2001 at 23:29 UTC | |
Re: unexpected close() success on (non-) filehandle
by demerphq (Chancellor) on Nov 21, 2001 at 19:39 UTC |
Back to
Seekers of Perl Wisdom