undeclared variables getting through in Strict Compilation mode

[Dr. Hawkins]

On Mon, Feb 16, 2015 at 3:55 PM, Bob Sneidar <bobsneidar at iotecdigital.com>
wrote:

> The simple way to avoid that in the future is what many have suggested for
> the eons we have been posting on this list: Name your variables in such a
> way that they *cannot* conflict.
>

But that's not the problem here :)

Livecode just plain didn't catch that a variable was undeclared . . . had
it been declared as local, it would have been an error.

Oh, and this didn't stop the shadow-name bug from biting with a vengeance
today, even with this going on . . .



-- 
Dr. Richard E. Hawkins, Esq.
(702) 508-8462