Musings on Architect, MVC, Nested Behaviors

J. Landman Gay jacque at hyperactivesw.com
Thu Dec 27 17:34:47 EST 2018


Yeah, I know breakpoints don't hurt in standalones but during active 
debugging you have to keep moving them around or deleting them to avoid 
unintended breaks. At least with red dots you can zap them all at once with 
a menu selection.

I've had more than one brush with the law you mentioned. :)
--
Jacqueline Landman Gay | jacque at hyperactivesw.com
HyperActive Software | http://www.hyperactivesw.com
On December 27, 2018 3:40:31 PM Mark Wieder via use-livecode 
<use-livecode at lists.runrev.com> wrote:

> On 12/27/18 10:21 AM, J. Landman Gay via use-livecode wrote:
>
>> I've heard you can insert hard-coded breakpoint commands in the script
>> instead but I haven't tried that yet. (Then you need to track them down
>> and remove them when they are no longer needed.)
>
> If you don't have remote debugging enabled then hard-coded breakpoints
> in a standalone app should have (almost) no effect. The mechanism in the
> engine that triggers breaks will fire, but if nothing is there to catch
> it then execution will continue as if nothing happened.
>
> That said, it's probably good practice to remove them before shipping
> anyway because of the Law of Unintended Consequences.
>
> --
>  Mark Wieder
>  ahsoftware at gmail.com
>
> _______________________________________________
> 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