> I always thought NI said "Do not abuse use of Global
> variables"?
>
We did. We also said not to abuse locals.
There are perfectly good uses for these and for the value property as
well, but they shouldn't be used for data manipulation and storage, and
rather for UI.
The big problem is that far too often, a person familiar with a textual
language will equate locals with textual variables and sequence frames
with a line of text. They will take statements like z= x*x+y and will
drop four local variable, three reads, a write, and a multiply and an
add. The problem with this sort of coding style is that it runs slowly,
it is hard to read, it has potential for lots of race conditions, it is
hard to maintain, and it takes a longer tim
e to write the code. If the
description above sounds familiar, please look at examples, read the
articles and manual on race conditions, and read about shift registers.
Greg McKaskle