From: matz@... (Yukihiro Matsumoto)
Date: 2003-12-18T02:35:54+09:00
Subject: Re: UnboundMethods Useless?

Hi,

In message "Re: UnboundMethods Useless?"
    on 03/12/18, Peter <Peter.Vanbroekhoven@cs.kuleuven.ac.be> writes:

|Where <some code> twice represents the same bit of Ruby code. Nobody can
|keep me from doing the above. If I understand correctly, Ruby doesn't
|allow the method to be copied from B to A, only from A to B. Now the
|reason you say that Ruby's test is correct, and it rightfully prevents us
|from copying a method from B to A, is that because the above Ruby code
|doesn't make sense, or because Ruby somehow internally fixes method m for
|use in B such that it is no longer fit to be used in A? Or rephrased, is
|it because moving the code is wrong at the Ruby level, or at the
|underlying implementation level?

Moving code is dangerous sometimes at C level.  And I didn't think it
is worth the cost of detecting whether moving is safe or not.

							matz.