From: Ross Konsolebox <lists@...>
Date: 2012-11-05T01:55:36+09:00
Subject: Re: Support for multiple Inheritance by classes

Peter Hickman wrote in post #1082774:
> Provide working code in the language of your choice that demonstrates a
> problem that is better served by multiple inheritance than single
> inheritance and you will have proven your point.

I believe I had explained enough. If it's about examples there are many 
around the web. If one is interested to know more about the advantages 
of having multiple inheritance there certainly are many around the web. 
It's not that I can't prove anything. I already encountered two 
situations twice and both were related to inheriting an external class 
where one of the other parent class was already a working class - that 
which could have solved things simpler and easier if MI was possible.

Come to think of it I could actually give you a summary of those 
classes.

Updater
OneTimeUpdater < Updater
DaemonUpdater < Updater

Then the utility was stable. After some time I decided to port it.

ServiceUpdater < DaemonUpdater, Daemon (External Class)

And this time this was not possible. I now have to decide whether I have 
to merge all codes from Updater to DaemonUpdater to make it work with 
ServiceUpdater or use another Class to Inherit Daemon that would control 
ServiceUpdater which would really be a hassle design-wise. No matter how 
you look at multi-inheritance would be the easiest form. Other 
variations would be just workarounds or redundant forms.

Now please reconsider again if you're going to question if my analogy 
with respect to the matter wasn't really that deep that there could have 
been something I missed for you to question me again. This is also just 
an example. An enough proof of concept as I could see it.

-- 
Posted via http://www.ruby-forum.com/.