From: Pat Maddox <pergesu@...>
Date: 2007-10-08T01:13:20+09:00
Subject: Re: The Case for Multiple-Inheritance

On 10/7/07, Austin Ziegler <halostatue@gmail.com> wrote:
> On 10/6/07, Trans <transfire@gmail.com> wrote:
> > The thing is (and maybe this will help clarify how I see this) the
> > more I work with Ruby the more I feel like the best code is always of
> > the form:
> >
> >   module M; end
> >   module X; end
> >   module Y; end
> >
> >   class Z
> >     extend M
> >     include X
> >     include Y
> >   end
> >
> > Such that everything is a module and classes are always just
> > compositions of modules. This provides maximum code reusability.
>
> I'll put it clearly: if I were running a Ruby consultancy and a
> programmer of mine used your methodology for everything (e.g., classes
> defined by composing modules), I would not keep that programmer on. It's
> a bad style. Sorry.

Agreed.  That looks painful.

Pat