From: Peter <Peter.Vanbroekhoven@...>
Date: 2003-12-17T23:54:29+09:00
Subject: Re: UnboundMethods Useless?

> There's a difference between freedom and a free-for-all or chaos.  In
> the case of module inclusion, of course you can do things that don't
> work:
>
>   module M
>     def x; strip; end
>   end
>
>   class C
>     include M
>   end
>
>   C.new.x      # undefined method strip
>
> but you've got a mechanism -- a language design -- in place which
> handles errors.  (And of course there's much more to that design.)  If
> you simply cut-and-paste methods (including core methods) from one
> object to another, you're bypassing this.

Yes, agreed. But we want to implement a higher level language mechanism,
comparable to what modules do, but to do that we need to be able to move
methods.

And moving core methods (I assume you mean those implemented in the C
core) is indeed likely to give big problems. I haven't considered that
yet. Even if Ruby would report an error if we tried to move a core method,
it would break our idea.

Peter