Error ring excluded in executable?

Question

Hello,
I encountered following strange behavior: when run in LabVIEW development, following error ring does its expected job as it also acts as a control flow control so that the reference is not destroyed before the loop terminates (see picture).
Strangely, when I build an executable and execute the VI via run-time, I the reference is destroyed WHILE the loop is still running. As if the error ring was not compiled into the executable.
Is it a LV bug?
Thanks,
Peter

Answer 1

Bokor wrote:
I managed to reproduce the problem in LabVIEW development if I disable debugging for this VI.
It seems to me that the compiler moves this part of the code outside the loop as static content. In this case, I would consider it as a bug, as the compiler shouldn't change the semantic of the program.
What do you think?
I don't see this as a bug.  There are some in LabVIEW R&D that say that using the error wire to force a data dependency is a hack.
I still go back to the fact that you should just be using your other error wire or wire your DVRs through your loop.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines