Re: Bareword vs. Indirect Filehandle behaviour

The obvious you're missing is that

    print OUT;
[download]

is just relying on yet another perl Do-What-I-Mean feature. The bareword OUT happens to be a filehandle, and the statement resolves to a bare print statement (to that filehandle). A bare print results in printing $_.

In fact, a bareword after print is always interpreted as a filehandle¹, no matter if it exists:

$ perl -wle 'print OUT'
Name "main::OUT" used only once: possible typo at -e line 1.
print() on unopened filehandle OUT at -e line 1.
[download]

With indirect filehandles that isn't the case: here the filehandle is a scalar holding a reference to a glob. Perl can't figure out what you mean (and imho ought not, anyways), so your variable's content gets printed. Only with print $expr LIST inspection of $expr is done.

$ perl -wle 'print $fh'
Name "main::fh" used only once: possible typo at -e line 1.
Use of uninitialized value in print at -e line 1.

$ perl -wle 'print $fh $bar'
Name "main::bar" used only once: possible typo at -e line 1.
Name "main::fh" used only once: possible typo at -e line 1.
Can't use an undefined value as a symbol reference at -e line 1.
[download]

Only in the latter case perl tries to resolve $fh to a filehandle.

¹) unless your bareword is a constant as in

$ perl -wle 'use constant OUT => "foo";print OUT'
foo
[download]

</update>

--shmem

_($_=" "x(1<<5)."?\n".q·/)Oo.  G°\        /
                              /\_¯/(q    /
----------------------------  \__(m.====·.(_("always off the crowd"))."·
");sub _{s./.($e="'Itrs `mnsgdq Gdbj O`qkdq")=~y/"-y/#-z/;$e.e && print}

Comment on Re: Bareword vs. Indirect Filehandle behaviour Select or Download Code

Replies are listed 'Best First'.
Re^2: Bareword vs. Indirect Filehandle behaviour by johngg (Canon) on Sep 19, 2006 at 10:37 UTC
Perl can't figure out what you mean (and imho ought not, anyways) ... I was sort of hoping that it could figure out what I mean because I think the `while (<IN>) {print OUT;}` construct is one of the neater features of the language. If I substitute an indirect filehande for a bareword one I still mean it to be a filehandle and give the same behaviour. Adding the `$_` is no big deal but the new behaviour breaks an idiom that I would guess is familiar to most and widely used. Cheers, JohnGG	[reply] [d/l] [select]
Re^3: Bareword vs. Indirect Filehandle behaviour by rodion (Chaplain) on Sep 19, 2006 at 10:57 UTC
Just one opinion, but I think your asking perl to extend an idiom rather than to not break one. The old idiom is still there. For me, it would be quite confusing if Perl extended the idiom so that "print $outFH;" was a write of "$_" to a specified filehandle, rather than a write of a variable to STDOUT. I have no doubt Perl could get it right, because it knows what variables are file handles and what aren't. I'd just have trouble reading it without my eyes getting caught in the wrong mode; I'd have to mentally back-track each time I read it.	[reply]
Re^4: Bareword vs. Indirect Filehandle behaviour by chromatic (Archbishop) on Sep 19, 2006 at 17:01 UTC
I have no doubt Perl could get it right, because it knows what variables are file handles and what aren't. In general, Perl actually can't know this. It's reasonably easy to make a Perl object that can act as a file handle as well as a string, depending on how you use it.	[reply]
Re^4: Bareword vs. Indirect Filehandle behaviour by johngg (Canon) on Sep 19, 2006 at 11:04 UTC
Good point. I'm looking at this as the bloke writing the code so I know it's a filehandle. The poor devil maintaining my code once I've moved on will, as you say, keep having to backtrack. Three extra keystrokes it is, then :-)	[reply]