What problem can arise from multiple inheritance in object-oriented design?

What problem can arise from multiple inheritance in object-oriented design?

• A. Ambiguity in member resolution and diamond problem.
• B. Memory leaks due to virtual tables.
• C. Performance overhead due to dynamic dispatch.
• D. Inability to share code between siblings.

Answer: (A)

The issue being tested is how multiple inheritance can introduce ambiguity and structural problems in an object hierarchy. When a class inherits from two parents that both provide a member with the same name, the derived class faces uncertainty about which parent’s member to use. This ambiguity in member resolution can make it unclear which function or data member should be accessed, leading to errors or the need for extra disambiguation in code. The diamond problem is a classic shape of this risk: if two base classes share a common ancestor, a derived class that inherits from both ends up having two paths to that ancestor. Without special handling, this can produce two separate copies of the common base subobject, causing duplication, inconsistent state, or further ambiguity about which base path’s members to reference. Languages often require techniques like virtual inheritance or explicit disambiguation to resolve these issues. Other listed concerns aren’t inherent consequences of multiple inheritance. Memory leaks from virtual tables and performance overhead from dynamic dispatch relate more to how virtual functions are implemented in general, not to multiple inheritance specifically. And rather than preventing code sharing, multiple inheritance can actually enable sharing through a common base, though with the noted risks.

The issue being tested is how multiple inheritance can introduce ambiguity and structural problems in an object hierarchy. When a class inherits from two parents that both provide a member with the same name, the derived class faces uncertainty about which parent’s member to use. This ambiguity in member resolution can make it unclear which function or data member should be accessed, leading to errors or the need for extra disambiguation in code.

The diamond problem is a classic shape of this risk: if two base classes share a common ancestor, a derived class that inherits from both ends up having two paths to that ancestor. Without special handling, this can produce two separate copies of the common base subobject, causing duplication, inconsistent state, or further ambiguity about which base path’s members to reference. Languages often require techniques like virtual inheritance or explicit disambiguation to resolve these issues.

Other listed concerns aren’t inherent consequences of multiple inheritance. Memory leaks from virtual tables and performance overhead from dynamic dispatch relate more to how virtual functions are implemented in general, not to multiple inheritance specifically. And rather than preventing code sharing, multiple inheritance can actually enable sharing through a common base, though with the noted risks.