multiple inheritence question

[Michael C. Starkie]

Car is a class, with four wheel variables. SUV is a class with four
wheel variables. Outback is a class that inherits from Car and SUV.
How many wheel variables does Outback have? (In general, how does
multiple inheritance work?)

[Victor Bazarov]

"Michael C. Starkie" <mi**@bogus.com > wrote...

Car is a class, with four wheel variables. SUV is a class with four
wheel variables. Outback is a class that inherits from Car and SUV.
How many wheel variables does Outback have? (In general, how does
multiple inheritance work?)

Well, in presented hierarchy the Outback object will have 8 wheels.
4 in its Car subobject, 4 in its SUV subobject. However, it would
probably be more correct to define the hierarchy this way:

class FourWheelVehicl e {
Wheel wheels[4];
...
};

class Car : public virtual FourWheelVehicl e { .. };
class SUV : public virtual FourWheelVehicl e { .. };
class Outback : public Car, public SUV { .. };

which will provide you with only one 'FourWheelVehic le' subobject in
Outback, and therefore only four wheels.

The reason I suggest extracting FourWheelVehicl e into a separate
base class is because there is too much common between Car and SUV
to ignore that. The common functionality and implementation should
be placed in the common base class.

Victor

[Dave Rahardja]

On Wed, 13 Aug 2003 23:34:53 GMT, "Michael C. Starkie" <mi**@bogus.com > wrote:

Car is a class, with four wheel variables. SUV is a class with four
wheel variables. Outback is a class that inherits from Car and SUV.
How many wheel variables does Outback have? (In general, how does
multiple inheritance work?)

Why does SUV not inherit from Car? That would solve your four-wheel problem.

Multiple inheritance is exactly what it says--your derived class will have a
combination of members from all of its parents.

[Senthilvel Samatharman]

> <snip>

class FourWheelVehicl e {
Wheel wheels[4];
...
};

class Car : public virtual FourWheelVehicl e { .. };
class SUV : public virtual FourWheelVehicl e { .. };
class Outback : public Car, public SUV { .. };

which will provide you with only one 'FourWheelVehic le' subobject in
Outback, and therefore only four wheels.

<snip>

A little confused victor, Is that not 12 wheels as Outback will have
one Car subobject,one SUV subobject and one FourWheelVehicl e subobject??

[Rolf Magnus]

Senthilvel Samatharman wrote:

<snip>
class FourWheelVehicl e {
Wheel wheels[4];
...
};

class Car : public virtual FourWheelVehicl e { .. };
class SUV : public virtual FourWheelVehicl e { .. };
class Outback : public Car, public SUV { .. };

which will provide you with only one 'FourWheelVehic le' subobject in
Outback, and therefore only four wheels.

<snip>

A little confused victor, Is that not 12 wheels as Outback will have
one Car subobject,one SUV subobject and one FourWheelVehicl e
subobject??

I could understand if you think 8, but where would the extra
FourWheelVehicl e come from?
Anyway, since Car and SUV inherit virtually from FourWheelVehicl e, there
will only be one copy of that base class in Outback. The Car and SUV
subobjects of Outback share their FourWheelsVehic le.