Re: RFC 174 (v1) Parse C<func($obj, @args)> as C<func $obj (@args)>

>I'd really like to see indirect object methods eradicated in Perl 6.
>Too many precidence problems, too many special cases, too confusing to
>teach.  Muddles up the otherwise simple function call.

[insert devil's advocate]

The nice thing about indirect objects is that they *read* better
in English.  C<give $sister @presents> is very readable as natural
language.  Furthermore, you to create list operators this way.
Finally, it lets you skip a whole lot of potentially slowdowning punctuation
compared with C<< $sister->give(@presents) >>, which needs at least four
more non-whitespace characters.

[delete devil's advocate]

Back when I was fighting with documenting the pain of current
indirect object pitfalls for the Ram and/or (new) Camel, I remember
once asking Larry whether, if he had it to do over again, whether
he wouldn't just toss out indirect objects.  Much to my surprise
(and some disappointment), he replied that he didn't really think
so.  I don't know whether this has changed since then.

--tom