Missing cRIO dependencies due to inheritance

Question

Hello,
I use LVOOP on a RT target where following dependencies are missing:
Class A{
  b: class B
In this case, a class C inheriting from B is not among the dependencies, unless C used explicitely.
This can cause to error, for example, if an instance of A is serialized and sent to the target.
It would be safe to add all classes inheriting from B to the dependencies. Instead, LabVIEW ignores these dependencies alltogether.
Is it a bug or a feature? Does LabVIEW support adding such dependencies?
Thanks,
Peter
Solved!
Go to Solution.

Answer 1

Bokor wrote:
You mean inheritance is a one-way dependency in the LabVIEW implementation, right? My parents know me, for example  I mean, it doesn't seem to me a global rule in OOP. Am I missing something?
This is true of all OOP implementations I've seen, in several languages. Inheritance is an "Is A" relationship - you can always substitute a child for the parent, but not vice versa. It would be impossible for a parent to know about ALL its children, since they could be added after the parent class is complete, and what good would it be for the parent to know about only some of its children, or to have a dependency on only those that existed prior to some point in time?
Bokor wrote:
Loading the class runtime is not an option in our case, I'm afraid. It's the "Unflatten from String" VI (deserialize), which throws an error if a class that is being deserialized is not loaded.
I wasn't trying to say that you should load the class at runtime, I was trying to explain that it is one reason that parent classes cannot have a dependency on their children. Here's another, somewhat complicated example where someone doesn't want the parent to include child classes automatically: http://lavag.org/topic/16714-class-dependency-linking/