Strict compilation mode
john at onechip.com
Sat Oct 5 14:09:19 EDT 2013
I guess I am lucky or there is some other, unknown, issue that is driving the "shadow" bug. I have occasionally messed up and redeclared a global as a local and received the error. In V5, as I recall, I would fix it and relaunch LC as a matter of course, In 6.1.2 RC1, the last time I received the warning, simply cleaning up code allowed it to run without a restart. Perhaps there is something buried in the stack file (some vestige you have no control over) that is driving the issue. I will consider my self lucky for now and hope my luck doesn't change.
On Oct 5, 2013, at 10:54 AM, "Dr. Hawkins" <dochawk at gmail.com> wrote:
> On Sat, Oct 5, 2013 at 10:07 AM, Peter Haworth <pete at lcsql.com> wrote:
>> I haven't used v6 much so far but you're scaring me! What's the problem?
>> I'm of course aware of the shadowing variable name issue; it happens
>> infrequently enough for me that I'm willing to put up with it. Is it worse
>> in v6?
> Yes, it's the shadows.
> In 5, we quit and restart. Maybe 1 time in 10, we have to do a couple of
> restarts with save with strictCompilation off.
> In 6, that doesn't always work. I had to give up. But after repeated
> failed tries in 6, I was able to open in 5 on the first attempt. I then
> tried 6, and it was still shadowed.
> Dr. Richard E. Hawkins, Esq.
> (702) 508-8462
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
More information about the Use-livecode