LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Parent VI recompile. When and why?

When parent VI is going to recompile itself due to changes in child VI, and when it is not?

0 Kudos
Message 1 of 4
(2,444 Views)

@MimiKLM wrote:

When parent VI is going to recompile itself due to changes in child VI, and when it is not?


Look here.  it was the second hit on a google search using this term: labview when does vi recompile

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 4
(2,442 Views)

To add "why":

The compiled code also contains a section called "inplaceness information". This section tells the caller (parent VI) if a parameter can be passed by reference (no copy) or by value (copy).

If changes in the subVIs can effect the way parameters are handled, the caller has to re-evaluate the inplaceness info, hence, it has to re-compile.

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Message 3 of 4
(2,413 Views)

Another thing just coming up in my mind:

If it is of concern for you that re-compilation of the caller (parent) changes the .vi-file so it has to be saved on disk again, you should use the option to separate compiled code from the vi-file.

 

Norbert

Norbert
----------------------------------------------------------------------------------------------------
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.
Message 4 of 4
(2,391 Views)