Re: new method dispatch rule (matz' proposal)

Evan Phoenix wrote:
> 1) Because of the current semantics, most ruby programmers treat 
> self.foo the same as foo(). I'm very wary of making functional style 
> behave much differently than normal method call style. It adds another 
> layer and complexity and strangeness that I believe we do not need nor 
> want. In fact, I think that it's a bug that private methods can only be 
> called using functional style. The method dispatch mechanism can easily 
> detect that the receiver of the method is the same all the current self 
> end look for private methods.

I agree here as well. Setting simpler logic for dispatching should be 
the goal, not more complicated logic. Having funcall logic now do more 
complicated dispatch logic than self.call logic will only make a 
confusing situation worse.

- Charlie