BreakPoint
Why some people say Local Variables are bad...
@altenbach wrote:
These race conditions can lurk unseen.! 😞
Yeah, I have a customer (used to be coworker) who just upgraded computers on an older test system. I thought for sure the race conditions in the main VI was going to bite them hard. Apparently they didn't upgrade enough.
What is even crazier is how he keeps track of the maximum value:
As I wrote here:
You seem to want to keep track of the maximum value. Also here you are making huge mistakes. First you append the value to the front of an array (which is much less efficient than adding to the end of an array). Then you keep the array in an uninitialized shift register, meaning that you retain old data between runs. Then you are growing the array forever, (or until you run out of memory). All you need to keep is a scalar value containing the current max!
Here's my a quick alternative that only needs to keep 8 bytes in memory, as opposed to searching for array max in an evergrowing array.
There is a new idea out to make local variables "good again", whatever that means.
See for yourself and either vote or abstain 😄
I will abstain. 😉
Why do we get all these horrible suggestions here?
"Wire as many local variables to all the case outputs to as yopu wish to see it blink as the code executes."
"Create local variable for all & inside loop make it true & outside make it false"
(If the guy would post his actual code, we could turn it into a state machine without any local variables in a few minutes....)
