From: James Edward Gray II <james@...>
Date: 2006-05-09T22:01:44+09:00
Subject: Re: Method call syntax

On May 9, 2006, at 12:10 AM, Yukihiro Matsumoto wrote:

> Hi,
>
> In message "Re: Method call syntax"
>     on Tue, 9 May 2006 05:48:13 +0900, mathew <meta@pobox.com> writes:
>
> |"Omission of parentheses around method arguments may lead to  
> unexpected
> |results. Note that the Ruby developers have stated that omission of
> |parentheses may be disallowed in future Ruby versions..."
> |
> |Is this true? I've been unable to find any reference to the alleged
> |unexpected results.
>
> It's in fact:
>
>  Omission of parentheses around method arguments for method calls in
>  the argument list may make programs hard to read / parse.
>
> for example,
>
>   p sprintf "the answer=%d\n",42
>
> warns like "warning: parenthesize argument(s) for future version", and
> recommended code should be
>
>   p sprintf("the answer=%d\n",42)

But you are still planning to allow them to be dropped in the non- 
ambiguous cases, right?  I notice you didn't add parenthesis to the p  
call above and I think it would be sad if we had to start writing:

   whatever.dup()

James Edward Gray II