From: Travis Whitton <whitton@...>
Date: 2003-04-10T02:00:29+09:00
Subject: Re: Proc Question

> In this case, call() would allow you to differentiate between a method
> and a proc object.

Hmm.... you've got a point there. I guess adding this feature could break
some people's code. I guess the solution would be to not create proc objects
with the same name as an existing method just the same as you shouldn't create
2 methods with the same name inside a class. I tested your example in Python
just to see what would happen, and the method took precedence over the lambda.
If Ruby copied that behaviour, then I don't believe any code breakage would
occur. At any rate, it's just an idea.

Cheers,
Travis