From: Bob Hutchison Date: 2012-11-06T01:12:46+09:00 Subject: Re: Support for multiple Inheritance by classes --Apple-Mail=_C78056BD-678D-4557-BEDB-914C10031F0B Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=iso-8859-1 Holy smoke! What is going on here?!? If you have ever used a Ruby module as a mixin then you've used multiple = inheritance. Period. There's no wiggle room. What is a mixin in Ruby is = part, only part, of what a general multiple inheritance mechanism = provides in other languages. And I'll bet that most of you who have used mixins thought they worked = out pretty well. So. You've used multiple inheritance and thought it was a good thing. WHY the near universal contempt for multiple inheritance? What's up? Cheers, Bob --Apple-Mail=_C78056BD-678D-4557-BEDB-914C10031F0B Content-Transfer-Encoding: quoted-printable Content-Type: text/html; charset=iso-8859-1
Holy smoke! What is going on = here?!?

If you have ever used a Ruby module as a mixin then you've = used multiple inheritance. Period. There's no wiggle room. What is a = mixin in Ruby is part, only part, of what a general multiple inheritance = mechanism provides in other languages.

And I'll bet that most of you who = have used mixins thought they worked out pretty well.

So. You've used multiple = inheritance and thought it was a good thing.

WHY the near universal = contempt for multiple inheritance? What's up?

Cheers,
Bob