2020 Interfaces and Multiple Inheritance

[blackburnite]

I understand the utility of and differences between the classes and interfaces and the solution to the diamond problem by disallowing dynamic VIs of the same name between 2+ interfaces inherited by a class.

But does anyone know what was the reasoning behind allowing multiple inheritance from Interfaces but not regular classes in LV2020?  Was this a technical constraint underneath due to potentially multiple sets of class data or more of a design decision to enforce certain best practices, or some combination?

[crossrulz · Accepted solution]

You might want to just give this a good read: LabVIEW Interfaces: The Decisions Behind the Design 

I have barely been able to skim it, but there is a whole section on the Call Parent Method that will kind of answer your question.