Jason Roelofs wrote:
> Even then, Ruby doesn't deal with method overloads via parameter
> lists, so there's a fundamental reason why it won't work:
>
> def foo(a)
> end
>
> def foo(a, b)
> end
>
> def foo(a, b, c)
> end
>
> foo(1) # => ArgumentError: wrong number of arguments (1 for 3)

I don't see how this relates to the OP's post at all.
def foo(a=1,b=2,c=3) end
foo(3)
works just fine. You don't need method overloading for that at all. The only 
thing that doesn't work is leaving parameters out in the middle and I at 
least can't see a good reason why this couldn't work the way the OP suggests.

-- 
Jabber: sepp2k / jabber.org
ICQ: 205544826