Saturday, February 10, 2007

Multiple inheritance issue

It turns out I was wrong about baby class inheritance. In addition to the abstract baby class (,which is responsible for most of your problems!) babies inherit a few things from both you and your partner. It’s a classic case of multiple inheritance and all that jazz.
The most important feature of any MI system is conflict resolution. How does the inheritor decide which inheritee implementation of a common method to use? Predictably – it tends to use the worst possible configuration it stumbles upon. What does that translate to?
For example: Mom likes to keep it neat while I like to crumple paper before throwing it in the tin can. The resulting combination at breakfast time is David keeping his part of the table neat by crumpling his toast and eggs and throwing them in the direction of the tin can.
I guess we have a few bugs to iron out here…

2 comments:

ZoRRo said...

Inheritance problems are easy... just wait 'till you get to "dll hell"... :D

Rory said...

Funny...

It's probably due to a race condition. Have you seen David running around madly? Perhaps there are multiple threads competing for shared attention and this is why you get this unexpected behavior.