Debugging plugins

[Peter Haworth]

Thanks Mark.

What I mean is, if errors in the revxxx stack are ignored (I assume that
means runtime errors?), is there some other way that the stack can
determine that they happened so they can be handled more gracefully?  Kinda
like an error in a try/catch loop.

Pete
lcSQL Software <http://www.lcsql.com>
Home of lcStackBrowser <http://www.lcsql.com/lcstackbrowser.html> and
SQLiteAdmin <http://www.lcsql.com/sqliteadmin.html>

On Wed, Jan 14, 2015 at 1:30 PM, Mark Wieder <mwieder at ahsoftware.net> wrote:

> Pete-
>
> Wednesday, January 14, 2015, 10:18:46 AM, you wrote:
>
> > If I understand this correctly, if a stack name begins with rev and
> > gRevDevelopment is false, any runtime errors in it are ignored? That's
> any
> > stack, not just IDE stacks?
>
> That is correct.
>
> > I don't suppose this would also enable some way to trap runtime errors
> and
> > report info about them, would it?
>
> I'm not following that. Runtime errors *are* trapped, unless I'm
> misunderstanding you, which I suppose is pretty obvious.
>
> --
> -Mark Wieder
>  ahsoftware at gmail.com
>
> This communication may be unlawfully collected and stored by the National
> Security Agency (NSA) in secret. The parties to this email do not
> consent to the retrieving or storing of this communication and any
> related metadata, as well as printing, copying, re-transmitting,
> disseminating, or otherwise using it. If you believe you have received
> this communication in error, please delete it immediately.
>
>
> _______________________________________________
> 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
>