Second one.
Dan
···
-----Original Message-----
From: ara.t.howard@noaa.gov [mailto:ara.t.howard@noaa.gov]
Sent: Thursday, March 02, 2006 9:05 AM
To: ruby-talk ML
Subject: Re: Confusion Over Keyword ArgumentsOn Fri, 3 Mar 2006, Berger, Daniel wrote:
>> -----Original Message-----
>> From: Yukihiro Matsumoto [mailto:matz@ruby-lang.org]
>> Sent: Wednesday, March 01, 2006 4:46 PM
>> To: ruby-talk ML
>> Subject: Re: Confusion Over Keyword Arguments
>
> <snip>
>
>> >How about "=" for keyword arguments instead
>> >(such as in python)?
>>
>> Unfortunately, assignments are legal in argument list in Ruby.
>>
>> matz.
>
> That can be made to work, with the understanding that '='
in a method
> call means 'keyword argument', not 'assignment', since there is no
> point in doing an assignment in a method call.
>
> # Method definition, '=' means assignment (of default value): def
> foo(bar, baz = 3)
> ...
> end
>
> # Method call, '=' means keyword
> foo(baz = 5, bar = 2)but is
foo baz = 5, bar = 2
a, b = foo(baz = 5), (bar = 2)
or
a = foo( (baz = 5), (bar = 2) )
??