Re: RFC 244 (v1) Method calls should not suffer from the action on a distance

[John Porter]

>   'foo'->bar($baz)
> 
> looks visually clattered, but C<<foo()->bar($baz)>> looks as if it expresses
> its meaning.  The default choice is done so that if you need other
> choice, your code does not look artificial.

Hear, hear!



>   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.

But [proposal:] Method calls should respect prototypes just like normal subs.

So that if bar is prototyped as bar($$), then the call is parsed as

  foo->bar($baz), $coon


-- 
John Porter

        We're building the house of the future together.