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

On 5/27/05, Pit Capitain <[e-mail]> wrote:
> 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.

Concur. I had a related situation while developing and debugging
PDF::Writer; I had some code that accessed #y as a reader ... until
the code assigned to y. Because I was relatively careful, it didn't
really hurt (until I extracted the code from the class into a separate
class entirely), but there are already cases where #y can be called
when y-the-local-variable is desired.

-austin
-- 
Austin Ziegler * [e-mail]
               * Alternate: [e-mail]