2020 Interfaces and Multiple Inheritance

blackburnite · ‎05-13-2020

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?

I saw my father do some work on a car once as a kid and I asked him "How did you know how to do that?" He responded "I didn't, I had to figure it out."

crossrulz · ‎05-13-2020

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.

There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5

LabVIEW

2020 Interfaces and Multiple Inheritance

2020 Interfaces and Multiple Inheritance

Re: 2020 Interfaces and Multiple Inheritance