Strict Compile Mode

Peter Haworth pete at lcsql.com
Tue Oct 9 14:12:39 EDT 2012


I didn't try that Bob but will give it a whirl.
Pete
lcSQL Software <http://www.lcsql.com>



On Tue, Oct 9, 2012 at 9:49 AM, Bob Sneidar <bobs at twft.com> wrote:

> Pete, out of curiosity, did you try "show stack tStackName"? It should be
> the identical command, but what the hey? Worth a shot. I do not know of any
> messages that get generated by simply making a stack visible, so it's
> doubtful that some message is generating a silent error and exiting to top.
>
> Bob
>
>
> On Oct 9, 2012, at 9:36 AM, Peter Haworth wrote:
>
> > Indeed!  Although recent frustrations have made me thing seriously about
> > using lock messages/wait a lot more even when there's no apparent reason
> > for doing so.
> >
> > For example, with help from a kindly customer, I discovered that the
> > following line of code in a script:
> >
> > "set the visible of stack tstackname to true"
> >
> > ... caused the rest of the script to not execute.  The fix was either to
> > move that line to the end of the script so there were no more lines to
> > execute after it or surround it with lock/unlock messages.  I've no doubt
> > there's a good explanation for that behavior but what it could possibly
> be
> > escapes me.
> >
> > Pete
>
>
> _______________________________________________
> use-livecode mailing list
> use-livecode at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-livecode
>



More information about the use-livecode mailing list