SystemVerilog OOP Mastery · All levels
No Multiple Inheritance: Interface Classes + Composition: Interview Questions
Interview Questions for No Multiple Inheritance: Interface Classes + Composition.
Interview questions
Q1. How do you emulate multiple inheritance in SV without losing clarity?
Answer: Use one inheritance chain for primary behavior, adopt additional capabilities via interface classes, and implement shared logic through composition/delegation.
Q2. What is the main design risk when replacing inheritance with composition?
Answer: Poorly managed object ownership and wiring can produce null handles or hidden coupling; constructors and contracts must clearly initialize and expose helper responsibilities.
Q3. Why is this pattern often preferable for verification code?
Answer: It keeps responsibilities explicit, makes testbench objects easier to mock/replace, and avoids ambiguous method resolution issues from multiple base classes.