How does LabVIEWs unusual implementation affect us in practical terms?
1. If you use uninitialized shift registers to store information, then you can get two different behaviors depending on the reentrancy of your VI. For a non-reentrant VI, you get a data sharing function that lets you move large quantities of information between parallel loops without making copies of it. For a reentrant VI, you get a reusable storage function that can keep independent copies each place you use it. There is a PowerPoint presentation and some example code related to uninitialized shift registers at: http://www.mooregoodideas.com/Downloads/Downloads.htm#ChangeDetector. 2. The second implication is that you can’t do recursion (functions that call themselves) easily in LabVIEW. In most languages, if a function is reentrant then it’s OK for it to call itself. In LabVIEW, that would require that the data storage for sub.vi would include a copy of the data storage for sub.vi which would … to infinity. You can do recursion in LabVIEW if you use VI Server to have a VI call its
