From: Austin Ziegler <halostatue@...>
Date: 2006-06-09T03:07:44+09:00
Subject: Re: Why the lack of mixing-in support for Class methods?

On 6/8/06, ara.t.howard@noaa.gov <ara.t.howard@noaa.gov> wrote:
> On Fri, 9 Jun 2006, Yukihiro Matsumoto wrote:
> > I don't like the name #inherit.  Since it is not a inheritance.
> i've suggested 'mixin' in the past
>
>    module M
>    end
>
>    class C
>      mixin M
>    end

Um. I think that's too confusing. The problem is that we want to be clear that:

  * #include only deals with the inclusion of instance-level methods
at the instance level.
  * #extend only deals with inclusion of instance-level methods at the
class/object level.
  * #??? includes both instance- and class-level methods at the
instance/class level.

In my mind, #mixin does not capture that, since the process of
#include *or* #extend is called mixing-in.

No, I don't have a better name. I thought of #blend, but that's just
too ... ugly.

-austin
-- 
Austin Ziegler * halostatue@gmail.com
               * Alternate: austin@halostatue.ca