The idea behind inheritance is that each class defines their methods how they need, so you don't need to be inspecting any code.

It seems like you're subclassing here just to re-use code, and that's not the idea of subclassing.

Maybe you should have helper member to do some of the tasks you need, instead of subclassing, and have both "Child" and "Parent" classes extend "Grandparent".

The main question you need to ask yourself is: "Is Child really a descendant of Parent,, Grandparent or eiter?" In other words, for every instance of Child, can I say it's a Parent?

If the answer is no, then you're subclassing wrongly: inheritance is supposed to mean something, not only code re-use (i.e. Ford IS ALSO a Car, not just "Ford" uses "Car" methods).

The idea behind inheritance is that each class defines their methods how they need, so you don't need to be inspecting any code.

It seems like you're subclassing here just to re-use code, and that's not the idea of subclassing.

Maybe you should have a helper member to do some of the tasks you need, instead of subclassing, and have both "Child" and "Parent" classes extend "Grandparent".

The main question you need to ask yourself is: "Is Child really a descendant of Parent, Grandparent or neiter?" In other words, for every instance of Child, can I say it's a Parent?

If the answer is no, then you're subclassing wrongly: inheritance is supposed to mean something, not just code re-use (i.e. Ford IS ALSO a Car, not just "Ford" uses "Car" methods).