Tx Andres, you are correct.

1) Use oneWayBecome: to implement twoWayBecome:

2) Use twoWayBecome: to implement oneWayBecome:

> Hi Eric.
>
> > 1) implementing 2 way become with a 1 way and
>
> > 2) a 2 way with a one way ?
>
> Oops, 1 oneWayBecame 2 or viceversa. In connection with this, the
> MethodFinder
> found an interesting message, #become:with:twoWay:. BTW, shouldn't the
> MethodFinder be called MessageFinder?

I would agree at some level, but a method is more than just a message.  From
a method you can get the classes that understand a message.  Since the
method finder brings up browsers on specific implementations, this is more
what a methog is than a message.  A message is simply the name of a method.
my 2 cents I guess ;->