From: David Vallner <david@...>
Date: 2006-11-14T07:07:29+09:00
Subject: Re: classes within classes

--------------enig2012FD265F47C7CAABF8305E
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Paul Irofti wrote:
> why can't you just use inheritage and mixins? would that generate a wor=
se
> design then what you currently have?
>=20

http://www.parashift.com/c++-faq-lite/multiple-inheritance.html#faq-25.4
- notably the comments in Rule #1

While a C++ text, the idea is relevant - C++ multiple inheritance was
used to implement mixins (Rule #2 in that article encourages that), and
the same rules should apply to Ruby as well.

In fact, most of the uses of normal inheritance I see in Ruby code is to
save you (a little) typing over composition, instead of overriding /
implementing the parent's methods. The latter is usually unnecessary
because of dynamic typing and blocks.

David Vallner


--------------enig2012FD265F47C7CAABF8305E
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFFWOyOy6MhrS8astoRAqodAJ4xQjLceZN710CTbVo1owiyjmdlNwCcDJno
wUKflsKA6GmJcbIQvOxXLVE=
=lHyi
-----END PGP SIGNATURE-----

--------------enig2012FD265F47C7CAABF8305E--