Re: Re: local vs my

That's right. Filehandles only ever exist as package "variables" in typeglobs. You have to localise them with local you can't create lexical filehandles with my

What about this?

open(my $fh, 'somefile') || die $!;
[download]

Comment on Re: Re: local vs my Select or Download Code

Replies are listed 'Best First'.
Re: local vs my by Arien (Pilgrim) on Sep 03, 2002 at 08:07 UTC
What about this? `open(my $fh, 'somefile') \|\| die $!;` When calling `open` with an undefined variable for the indirect filehandle (`$fh` in this case), `open` will stick a reference to the "real" filehandle in the indirect filehandle. `$fh` is a lexical, what it refers to is not. — Arien	[reply] [d/l] [select]
Re: Re: Re: local vs my by davorg (Chancellor) on Sep 03, 2002 at 08:10 UTC
Excellent point. But that is, of course, a relatively new innovation :) -- <http://www.dave.org.uk> "The first rule of Perl club is you do not talk about Perl club." -- Chip Salzenberg	[reply]
Re^4: local vs my by Aristotle (Chancellor) on Sep 03, 2002 at 13:23 UTC
The innovation is only in the autovivification. It was awkwardly possible before as well, you just had to do the job yourself: `use Symbol; my $fh = gensym; open $fh, $filename;` [download] Makeshifts last the longest.	[reply] [d/l]


No such thing as a small change
	PerlMonks