Inheritance Trouble

[zippy747]

I would like to have a base class that does some work and can be
instantiated.

class a
{
public:
virtual int foo() { return 0; };
virtual int bar() { return 0; };
};

I would like to have a derived class that does some slightly different
work and can be instantiated.

class b : public a
{
public:
virtual int foo() { return 1; };
};

I would like to have another derived class that does some slightly
different work in a different area and can be instantiated.

class c : public a
{
public:
virtual int bar() { return 2; };
};

I would like to have another derived class that takes some
functionality from b and some from c:

class d : public b, public c
{

};

I would like the output of the following code

int main()
{
a theA;
printf("%i\n", theA.foo());
printf("%i\n", theA.bar());

b theB;
printf("%i\n", theB.foo());
printf("%i\n", theB.bar());

c theC;
printf("%i\n", theC.foo());
printf("%i\n", theC.bar());

d theD;
printf("%i\n", theD.foo());
printf("%i\n", theD.bar());

return 0;
}

to be:

0
0
1
0
0
2
1
2

Obviously, it isn't since theD doesn't know if it should use
foo()/bar() from the a->b->d inheritance tree or the a->c->d
inheritance tree.
What is the proper way to meet these requirements?

Thanks,
-zip

[Victor Bazarov]

zippy747 wrote:

I would like to have a base class that does some work and can be
instantiated.

[...]
What is the proper way to meet these requirements?

Read about virtual inheritance.

V

[jeffc]

"Victor Bazarov" <v.********@comAcast.net> wrote in message
news:_7****************@newsread1.dllstx09.us.to.v erio.net...

zippy747 wrote:

I would like to have a base class that does some work and can be
instantiated.

[...]
What is the proper way to meet these requirements?

Read about virtual inheritance.

I don't think that will solve his problem, because virtual inheritance relates
to state, and he is trying to define behavior, correct?

[Victor Bazarov]

jeffc wrote:

"Victor Bazarov" <v.********@comAcast.net> wrote in message
news:_7****************@newsread1.dllstx09.us.to.v erio.net...

zippy747 wrote:

I would like to have a base class that does some work and can be
instantiated.

[...]
What is the proper way to meet these requirements?

Read about virtual inheritance.

I don't think that will solve his problem, because virtual inheritance relates
to state, and he is trying to define behavior, correct?

Probably. I didn't spend enough time to understand the OP's problem.
Perhaps it can be solved with casting the 'theD' object to 'b' or 'c'
or 'a', explicitly.

V

[Olivier Azeau]

zippy747 wrote:

I would like to have a base class that does some work and can be
instantiated.
[SNIP]
I would like to have another derived class that takes some
functionality from b and some from c:

class d : public b, public c
{

};
[SNIP] Obviously, it isn't since theD doesn't know if it should use
foo()/bar() from the a->b->d inheritance tree or the a->c->d
inheritance tree.
What is the proper way to meet these requirements?

Maybe you can try using the "using" directive to specify which foo and
bar you want class d to use.

[Jay Nabonne]

On Wed, 15 Dec 2004 07:49:39 -0800, zippy747 wrote:

I would like to have a base class that does some work and can be
instantiated.
<snip>
I would like to have another derived class that takes some
functionality from b and some from c:

class d : public b, public c
{ public:
virtual int foo() { return b::foo(); }
virtual int bar() { return c::bar(); } };

Works?

- Jay

[marieddu78]

class b : public virtual a

class c : public virtual a

[jeffc]

"marieddu78" <ma************@vivacity.it> wrote in message
news:74******************************@localhost.ta lkaboutprogramming.com...

class b : public virtual a

class c : public virtual a

This is virtual inheritance. How exactly does this solve the OP's problem?
Virtual inheritance exists to avoid making 2 copies of the base class. This
doesn't have anything to do with the fact that his D object doesn't know which
function to invoke.

[Olivier Azeau]

Jay Nabonne wrote:

On Wed, 15 Dec 2004 07:49:39 -0800, zippy747 wrote:

I would like to have a base class that does some work and can be
instantiated.

<snip>

I would like to have another derived class that takes some
functionality from b and some from c:

class d : public b, public c
{

public:
virtual int foo() { return b::foo(); }
virtual int bar() { return c::bar(); }

};

Works?

- Jay

What about

class d : public b, public c
{
public:
using b::foo;
using c::bar;
};

?

[Jay Nabonne]

On Thu, 16 Dec 2004 18:48:49 +0100, Olivier Azeau wrote:

Jay Nabonne wrote:

What about

class d : public b, public c
{
public:
using b::foo;
using c::bar;
};

?

One question is: how should D behave when used in the context of a B (that
is, polymorphically)? That's one thing unclear from the OP. I don't think
the "using" strategy will affect polymorphic behavior. So the correct
approach is determined by the unstated needs... :)

- Jay