>> foo->bar($baz, $coon)
>> should be made synonymous with
>> foo->bar $baz, $coon
>>
>> I can see no ambiguity in this call, but it not always works with Perl5.
Arrow invocation does not a listop make. Only indirect object invocation
style does that.
print STDOUT $foo, $bar, $glarch;
is a list op.
STDOUT->print $foo, $bar, $glarch;
is not, and, in fact, is a syntax error. You *must* use parens for
the arrow invocation's arguments. You *may* use them with I/O style.
--tom
- RFC 244 (v1) Method calls should not suffer from the a... Perl6 RFC Librarian
- Re: RFC 244 (v1) Method calls should not suffer f... Michael G Schwern
- Re: RFC 244 (v1) Method calls should not suffer f... Nathan Wiger
- Re: RFC 244 (v1) Method calls should not suff... John Porter
- Re: RFC 244 (v1) Method calls should not suffer f... John Porter
- Re: RFC 244 (v1) Method calls should not suff... Tom Christiansen
- Re: RFC 244 (v1) Method calls should not suffer f... Nathan Wiger
- Re: RFC 244 (v1) Method calls should not suff... Ilya Zakharevich
- Why -> cannot autoquote the LHS (was Re: RFC 2... Nathan Wiger
- Accessing perl's command line switches Chaim Frenkel
- Re: Why -> cannot autoquote the LHS (was R... Glenn Linderman
- Re: RFC 244 (v1) Method calls should not suffer f... Ilya Zakharevich
- Re: RFC 244 (v1) Method calls should not suff... Nathan Wiger
- Re: RFC 244 (v1) Method calls should not ... Ilya Zakharevich
- Re: RFC 244 (v1) Method calls should ... Nathan Wiger
- Re: RFC 244 (v1) Method calls sh... Ilya Zakharevich
