Explicit Variables again

[Peter Haworth]

Sounds like this is turning into a "There are 2 types of Livecode coders,
those who..." situation!

Marks' comment below hit the nail on the head for me.  All I can say is
that when I converted my first stack to use explicit variables, it turned
up a couple of nasty bugs lurking in seldom used parts of the code that
would have surfaced to surprise me at some point in the future.  I can also
recall more than one occasion where I spent a not insignificant amount of
time debugging a problem cause by a misspelled variable.  So, for me, I am
more than happy to take the few extra seconds to type a local command,
knowing that it will almost certainly save me from myself.

But others may, and do, think differently.  It's a personal opinion.  Maybe
those of us who do use explicit variables should have our plugins display a
message at startup, something like:

WARNING!! THIS CODE CONTAINS VARIABLES OF AN EXPLICIT NATURE.

Pete
lcSQL Software <http://www.lcsql.com>



On Fri, Oct 19, 2012 at 8:48 AM, Mark Wieder <mwieder at ahsoftware.net> wrote:

> <sigh> Look, as a qa engineer let me state the truism that the earlier
> in the development process you can find bugs, the cheaper it is to fix
> them. The idea of enforcing explicit variable declarations is to catch
> some bugs at compile time rather then waiting for them to appear at
> runtime and force you to debug what happened.
>