From: Robert Dober <robert.dober@...>
Date: 2007-02-05T18:47:10+09:00
Subject: Re: Mixin advantage

------=_Part_52513_29287483.1170668828269
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

On 2/5/07, Minkoo Seo <minkoo.seo@gmail.com> wrote:
>
> Hi.
>
> Please proofread whether the following statement (written by me) about
> Mixin in Ruby is true:
>
> "Mixin is the way to incorporate certain functionalities into a class
> without messing up inheritance hierarchy. Especially, Mixin in Ruby is
> a clever way of implementation inheritance."


... multiple inheritance...

The rest is difficult to  judge and I am not qualified to make a strong
statement.
But be aware that even Mixins can be confusing for the unwary sometimes
there was a recent thread about it.

I've seen no article mentioning implementation inheritance when
> explaining mixin though I believe it is especially in contrast with
> interface inheritance.
>
> Sincerely,
> Minkoo Seo
>
>
>
Cheers
Robert

-- 
We have not succeeded in answering all of our questions.
In fact, in some ways, we are more confused than ever.
But we feel we are confused on a higher level and about more important
things.
-Anonymous

------=_Part_52513_29287483.1170668828269--