From: transfire@...
Date: 2006-06-09T03:32:40+09:00
Subject: Re: Why the lack of mixing-in support for Class methods?


Yukihiro Matsumoto wrote:
> Hi,
>
> In message "Re: Why the lack of mixing-in support for Class methods?"
>     on Fri, 9 Jun 2006 00:49:19 +0900, "Alder Green" <alder.green@gmail.com> writes:
>
> |I see your and Dblack's point about the need for an #include that
> |won't inherit the class methods. And I agree that it's probably a good
> |idea to keep #include behaving as it does right now. So adding a
> |separate #inherit seems like a very good idea.
>
> I don't like the name #inherit.  Since it is not a inheritance.

I knew you were going to say that ;) I actually hesitated to suggest
it, but I haven't thought of anything better. But I would like to point
out an interesting (albiet currently illegal) equivalency:

  module Beanable
    def self.pod
      "oooooo"
    end
  end

  class Beanbag
    extend (class << Beanable; self; end)
  end
 
T.