It is a way to add a (reusable) behavior to several classes.

A Mixin is a separate class that through MI adds some functionality. It is the way it is designed
and used that causes it to be called a Mixin rather than a "super" or "parent" class.

See:

http://www.cs.rice.edu/CS/PLT/Publications/icfp98-ff/paper.shtml

http://www.psg.com/~dlamkins/sl/chapter07.html

"Object Oriented Programming in Common Lisp", Sonya E. Keene treets it well too.


Alex

> -----Original Message-----
> From: squeak-dev-admin at lists.squeakfoundation.org
> [mailto:squeak-dev-admin at lists.squeakfoundation.org]On Behalf Of Hans
> Beck
> Sent: Friday, October 11, 2002 3:09 PM
> To: squeak-dev at lists.squeakfoundation.org
> Subject: Re: is Missing multiple inheritance in sqeak a drawback ?
>
>
> Hi,
>
> Alex Peake wrote:
> > There is one aspect of MI that I find quite practical, from a productivity and a manageability
> > perspective, and that is Mixins (as in CLOS, PLT Scheme, ..).
> >
> > This allows localization of specializations, with complete sharing, excellent
> manageability and no
> > need to build "wrapper" functions (as with Has-A).
> >
> > Alex
> >
>
>
> What are Mixins ? my knowlegde of Scheme and CLOS is very poor (and old
> too :-((
>
> Thanks.
>
> Greetings
>
> Hans
>
>
>
>