Quote:
Originally Posted by Greg McKaskle
If you have a VI that you can send to me that shows nested loops causing a 30 minute or even a 30 second compile of a single VI, please send it. In 20 years of using and writing LV, I've never seen this.
Greg McKaskle
|
I can't say I have any vis with nested loops because our team has avoided programming with them for the past several years due to a noticeable improvement in compile when they stopped using them. After doing some research(post-posting the previous post, say that five times fast
), it seems that this could have been a result of a trigger happy watchdog who wasn't being fed. I was not personally on the team, so I am spurting out secondhand information and it is possible that whatever was causing our problems has been fixed in more recent versions of LabView. I apologize if I am spreading false info on these forums and I realize I should have put a qualifier on that statement. However, our team has never had much of a problem avoiding nested loops, thanks to the ingeniousness of the folks at NI who added in a flat-sequence structure
. Labview is my personal language of choice for frc regardless of whether or not nested loops are an issue because of its easy-to-learn interface and built-in tools and help.