Strict Compile Mode

Guglielmo Braguglia guglielmo at
Thu Oct 11 14:35:01 EDT 2012

Hi Pete,
this happen very often also to me ...

... I don't know, but ... if you are debugging your code 
stepping-by-stepping and you stop the execution, some time LiveCode 
create this problem.

The only solution is to save the stack, close LiveCode (/is not 
sufficient to close the stack/) and restart ... your stack is ok, your 
code also and if you compile ... NO ERRORS!

Don't ask why ... :-(


On 11.10.2012 19:18, Peter Haworth wrote:
> Finished converting all the scripts in a stack to include local variable
> definitions and got clean compiles of everything a couple of days ago.
>   Today, I made some changes to a handler that did not involve any new
> variables.  When I compiled, I got the error message "local: name shadows
> another variable or constant" pointing to a line in the same script but a
> completely different handler which previously compiled OK.
> I checked all my the local commands in the script and they are all within
> handlers except for one and it does not refer to the variable named in the
> error message.  There are no global definitions in the script.
> Are there any other reasons for this error?  I'm at a loss to understand
> why this script compiled with no problems originally and now is flagging
> errors on my local definitions.
> Pete
> lcSQL Software <>
> _______________________________________________
> use-livecode mailing list
> use-livecode at
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:

More information about the Use-livecode mailing list