>> If they have diverging interfaces such that the contracts conflict 
>> with
>> each other, then maybe they should two subclasses with a common
>> superclass, possibly Object or possibly a new class representing 
>> whatever
>> they might have in common.
>
> That would violate Matz ``less-class-ism''  and it is not very 
> difficult
> to make an inheritance chain Method < UnBoundMethod meaningful
> (imo it kind of feels ``right'') and last but not least it should be 
> easy
> to come by a patch implementing this.  See the previous thread
>
>
Not necessarily: I don't believe that Unbound should inherit from 
Method: I think they should both inherit from Object. All they really 
share is 'arity', and Proc has that too.

Cheers


Dave