You can't use subscripts in a variable used as a filehandle. This applies to the diamond operator as well as print statements. I.e. print $_[0] "foo"; won't work either.

Update: Here's the relevant bit from perldoc perlop:

     If what's within the angle brackets is neither a filehandle
     nor a simple scalar variable containing a filehandle name,
     typeglob, or typeglob reference, it is interpreted as a
     filename pattern to be globbed, and either a list of
     filenames or the next filename in the list is returned,
     depending on context.  This distinction is determined on
     syntactic grounds alone.  That means "<$x>" is always a
     readline() from an indirect handle, but "<$hash{key}>" is
     always a glob().  That's because $x is a simple scalar
     variable, but "$hash{key}" is not--it's a hash element.
[download]

By the way, please test your example code before pasting it. Yours had several errors unrelated to the issue you are seeing.

-sauoq
"My two cents aren't worth a dime.";

thank you very much, that's what I needed...

--
jey

use FileHandle;

sub in { $_[0]->getline }
sub out { $_[0]->print(@_[1..$#_]) }

out \*STDOUT, in \*STDIN;
[download]

MyFonc() doesn't do anything with its argument. The split call acts on $_, not @_. Your MyFonc might take whatever it gets from $_ as a glob, giving a list of file names to iterate over.

MyFunc() will work if you shift in the glob reference first. When MyFonc gets called, *FH is at eof. In between the two, call seek

myFunc(\*FH);
seek FH, 0, 0;
myFonc(\*FH);  # the repaired one :)
[download]

I guess you mean shift, not split. (Update: the original post has now been updated. It was a split in stead of a shift.)

Sorry for the split instead of the shift...

--
jey

my $fh;
open $fh, "<$myFile" or die "blah";
myFunc($fh);

sub myFunc {
    my $fh = shift;
    while(<$fh>) {
        # do something
    }
}
[download]

First of all, you're using a reference to a glob as a filehandle - that's bound not to work.

Uh... "Bound not to work"?

perl -le '$x = \*STDOUT; print $x "Bzzzt."'
[download]

That used to be the "accepted" way of passing handles around... :-)

-sauoq
"My two cents aren't worth a dime.";

Yes, you're right. I should have tested it out before making that claim. :) I still prefer lexically-scoped filehandles whenever possible, but thanks for pointing out my mistake.

---

The computer can't tell you the emotional story. It can give you the exact mathematical design, but what's missing is the eyebrows. - Frank Zappa

On the contrary, it bounds to work. As sauoq pointed out in his 1st reply, the problem is on the receiving side, not the passing side.

I tested, his Fonc actually worked, but not Func. You must have noticed that it passes the handler to them in exactly the same way, but Fonc and Func receive the parameter differently.