From: Yukihiro Matsumoto <matz@...>
Date: 2009-01-20T16:09:48+09:00
Subject: [ruby-core:21452] Re: Proposal: Module#copy_method

Hi,

In message "Re: [ruby-core:21439] Re: Proposal: Module#copy_method"
    on Tue, 20 Jan 2009 05:14:49 +0900, Charles Oliver Nutter <charles.nutter@sun.com> writes:

|> I am afraid it's too much restriction for OP's use-case, since so many
|> methods are implemented in C.
|
|The JRuby example I posted does filter out native methods. I agree 
|that's a necessary minimum restriction in order to support this. I do 
|not think it's too limiting a restriction for copy_method to be useful 
|though.

Although Yehuda (OP) also suggested the same limitation, I am strongly
against.  Ruby does provide little or no distinction between C
implemented methods and Ruby implemented ones.  I would not feel
reasonable when I see unexpected error to copy some methods, where
other methods can be copied.  This enhancement cannot have a place in
the built-in methods.  It should be separated library at most.

							matz.