In article <992245528.412022.1311.nullmailer / ev.netlab.zetabits.com>,
Yukihiro Matsumoto <matz / zetabits.com> wrote:

>Yes.  Method objects are created each time you invoke "method". 
>It's for "handling a method as an object", not for comparison.

Okay.  I thought that == was supposed to be for logical equivalence,
not necessarily "same object" equivalence?  Or is that just === ?

Anyway, I'm thinking that maybe it would be more intuitive to have ==
or === return true for two different Method objects if they both
reference the same underlying method.  What do you think?

--Mirian