Re: will callable objects be more general in Ruby 1.9?

Eric Mahurin schrieb:
> In terms of compatibility, I assume you are referring to the
> fact that if you have a local variable f (callable or not), f()
> will try to call it even if the method f exists (in 1.9).  I
> like this new behavior (local variables always override), but
> to preserve compatibility couldn't you just change the
> priority? - f() would prefer calling method f over calling
> local variable f.

Please don't. Otherwise, adding a method to a class could break 
previously working methods.

Regards,
Pit