On Sunday 27 June 2004 19:40, Gavin Sinclair wrote:
> Austin Ziegler wrote:
> > The only valuable form of object replacement, IMO, is
> > replacing a proxy object with a real object.
>
> That sounds about right to me.  Aren't there two separate issues here?
> 'become', to me, means "become another **object**", not "change your
> class".
>
> I don't even know what
>
>   x = X.new
>   x.class = Y
>
> is supposed to mean.  But I do understand the idea behind this:
>
>   x = X.new
>   y = Y.new
>   x.become y

That's funny, because the first one makes immediate sense to me, but I'm not 
sure what the second one does.

What happens when x becomes y?  Methods are replaced?

	Sean O'Dell