Question

I’m developing a API in which the class A is derived as class B.

if a API user want to extend the functionality of both class A and class B at application level, then there will be problem.

suppose application user come up with class AX extending class A, and class BX extending class B. In this instance user does not get the expected behavior for class BX since class Bs’ base class is class A NOT class AX.

Thought : Application user may extend the class BX using both class B and class AX, but in this case I think there will be known diamond behavior.

I would like know, any standard way of resolving this issue.

Answer 1

A class inheriting from a template parameter is also an option. Pseudo-code:

class A;

template<typename WhichA>
class B : public WhichA;

class AX : public A;

class BX : public B<AX>;