LSTOP indirob argexpr          /* print $fh @args */
FUNC '(' indirob expr ')'      /* print ($fh @args */
LSTOP listexpr                 /* print @args */
FUNC '(' listexprcom ')'       /* print (@args) */
[download]

I'm not sure I agree that this is an "indirect object", though. It looks like the parser's trying to convert anything that looks like a filehandle into a filehandle.

FUNC '(' indirob expr ')'      /* print ($fh @args */
[download]

Hmm, so it specifically allows parens there! I had no idea--I thought they would defeat this way of parsing.

Also, is print special? I don't recall foo (bar (5)); ever trying to call bar->foo(5) instead.

Is that why you don't agree that indirob is the right characterization for it?

—John

I can see that scanfile will see that it was called with "wantarray" But why does print think that's an indirect object...

I don't have an answer for you, but I have yet to find a print statement that Deparses differently depending on the outer parens. I think it might be a red herring, which is why I left them off in my previous example.

% perl -MO=Deparse -e 'print abc'
     print abc $_;
% perl -MO=Deparse -e 'print(abc)'
     print abc $_;

# when you said 'indirect object' I thought this was
# what you thought was going on....
% perl -MO=Deparse -e 'print abc def'
     print 'def'->abc;
% perl -MO=Deparse -e 'print(abc def)'
     print 'def'->abc;

% perl -MO=Deparse -e 'open abc; print abc def'
     open abc;
     print abc 'def';
% perl -MO=Deparse -e 'open abc; print(abc def)'
     open abc;
     print abc 'def';

% perl -MO=Deparse -e 'print abc:: def'
     print abc 'def';
% perl -MO=Deparse -e 'print(abc:: def)'
     print abc 'def';

% perl -MO=Deparse -e 'print abc:: ()'
     print abc ();
% perl -MO=Deparse -e 'print(abc:: ())'
     print abc ();

% perl -MO=Deparse -e 'print abc::def ()'
     print abc::def ();
% perl -MO=Deparse -e 'print(abc::def ())'
     print abc::def ();
[download]

-Blake