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

Hi,

In message "Re: will callable objects be more general in Ruby 1.9?"
    on Fri, 27 May 2005 08:43:06 +0900, Eric Mahurin <[e-mail]> writes:

|I was kind of looking forward to the further unification of
|objects - all objects being callable like methods already are.

I'm afraid it's just like making Common Lisp into Scheme.
I thought that local variable + parentheses idea would make it without
huge language change, but it turned out to be a not-so-good idea.

|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.

The priority idea is interesting.  My two concerns are:

  * it might make it hard for humans to understand what code does, by
    introducing runtime ambiguity.
  * I'm not sure if yacc allows that kind of priority resolution.

							matz.