11-30-2012 06:45 AM
Performance of the property node would likely be the worst. Not sure if Shared Variables would be in 2nd or 1st place though.
The concern is not the performance issue, but rather the abuse issue. Why use a Local or Global or Shared Variable or Property Node when a simple wire will do the trick?... Many people (from text based background) think it is necesary to create a "variable" when writing code in LabVIEW. We, of course, know that it is not necessary. 🙂
11-30-2012 07:17 AM
I always like to overexagerate 🙂
Other things I've seen before are even worse..
Instead of local variables I saw some even use network published shared variables, OPC servers or (last but not least) File I/O... 🙂
11-30-2012 11:21 AM
wow... I thought I had seen it all.,. File IO??? wow 😮
11-30-2012 11:27 AM - edited 11-30-2012 11:28 AM
Another abuse causing a race condition.. seen here...
Below is a portion of the code.. More abuse not shown..
11-30-2012 12:47 PM
Lets "Go Madden" On that.
"Theres the PSD(prepare Shut Down) Enqueued" but Event element blows the call... but theres the dequeue right there just missing the handoff with event queue again. Look at the machine GO Event element is really knocking states around down there and trigger stop gets right into the action. Looks like PSD gets another swat at carrying it to the queue. Whats that the event loop exit came out of nowhere and just destoyed the queue! there variable everywhere piled deep on the field. The refs will never get this straightened out.
![]()
11-30-2012 01:13 PM
Listen to this music while reading his text.. 🙂
11-30-2012 01:21 PM
11-30-2012 01:42 PM
O-M-G 😮
11-30-2012 01:54 PM
Scary thing is that everything apparently worked before updating to 64bit windows .... These race conditions can lurk unseen.! 😞
11-30-2012 02:02 PM
very scary indeed...