Error info about try/catch

[ale870]

Hello,

I'm using try/catch to detect some errors. This structure return some error numbers but I cannot "decode" them.
Please can you give me a reference to read them?

For example (trivial example):

Code: Select all

try
   get 5/0
catch err
  answer err
end try

I get:
379,337,6
223,337,1

So... ???

[Klaus]

Hi ale870,

what you see are the hints rom the ERRORDIALOG, check the dictionary for more info.
...
The executionError parameter is a standard LiveCode error backtrace in the form:
<error-code>,<line-number>,<column-number>[,<hint>]
...

Best

Klaus

[ale870]

Hi ale870,

what you see are the hints rom the ERRORDIALOG, check the dictionary for more info.
...
The executionError parameter is a standard LiveCode error backtrace in the form:
<error-code>,<line-number>,<column-number>[,<hint>]
...

Best

Klaus

Great thank you!
But the problem is not yet solved since, reading the documentation and making tests, error codes are stored inside revErrorDisplay, and that stack is available only when using the IDE (so I cannot get info during runtime
It is crazy that I cannot include that stack while I distribute my application.
Any workaround?

[Neurox66]

Hi,

read this...

http://runtime-revolution.278305.n4.nab ... 53157.html

Paolo

[ale870]

Hi,

read this...

http://runtime-revolution.278305.n4.nab ... 53157.html

Paolo

Thank you! That RevOnline Error Lookup is amazing! I can extract and embed those error codes inside my app!
Thank you again, I solved my problem!

[dbeugeling]

Hi,

The link is no longer valid.
Is there an updated one?
Thanks

Dirk

[Klaus]

Dag Dirk,

here a little stack from Jacque Gay, which does it locally.


Best

Klaus

[FourthWorld]

It seems weird to me that there isn't a documented function for looking up the error string from the error code number.

[jacque]

It seems weird to me that there isn't a documented function for looking up the error string from the error code number.

It's in the entry for errorDialog in the dictionary.

@klaus Richard and I co-wrote the error lookup stack. It's also available in the LC user examples online.

[FourthWorld]

It seems weird to me that there isn't a documented function for looking up the error string from the error code number.

It's in the entry for errorDialog in the dictionary.

Thank you. I'd forgotten about the scriptExecutionErrors.

That these sorts of questions keep coming up several times a year suggests a rethink on error handling may be helpful. ErrorDialog is used in many contexts unrelated to even potentially showing a dialog window, and there are opportunities to streamline decoding the error data, as well as making error handling more consistent than the current collection of sometimes rules (sometimes we check errorDialog, sometimes we need to use sysError, sometimes we check the result, sometimes we need to structure our code specifically for error handling using try/catch...).

[stam]

I've just noticed that scriptExecutionErrors returns empty in standalones, further reducing it's value...
You'd need to duplicate scriptExecutionErrors in your stack if you wanted to provide proper feedback on errors in a standalone. Not any degree of difficult, but why the extra step?

[jacque]

I've just noticed that scriptExecutionErrors returns empty in standalones, further reducing it's value...
You'd need to duplicate scriptExecutionErrors in your stack if you wanted to provide proper feedback on errors in a standalone. Not any degree of difficult, but why the extra step?

Maybe because there is no debugger included in standalones.

[stam]

I've just noticed that scriptExecutionErrors returns empty in standalones, further reducing it's value...
You'd need to duplicate scriptExecutionErrors in your stack if you wanted to provide proper feedback on errors in a standalone. Not any degree of difficult, but why the extra step?

Maybe because there is no debugger included in standalones.

Do you need a debugger to get the error codes? I ask because the standalone settings have a 'bug reports' section which I presume relates to LC error codes being generated. How else would this be triggered? And I haven't checked but had assumed the error numbers returned would do so in standalones as well, or is this also not the case?

(Also - Richard elegantly showed a debugger that can be included in a standalone...)

[jacque]

The scriptExecutionErrors seems to be an IDE thing. If you want to catch all errors, not just the ones that LC reports in standalones (i.e., catch silent errors) you can use an errorDialog handler. That's what I usually do.

Code: Select all

on errorDialog pErr
  answer "Error:" && the params &cr& pErr
end errorDialog

Edit: Error info is generated in a standalone but unless they are fatal, users won't see a dialog. The above catches all of them.

[stam]

The scriptExecutionErrors seems to be an IDE thing. If you want to catch all errors, not just the ones that LC reports in standalones (i.e., catch silent errors) you can use an errorDialog handler. That's what I usually do.

Errrrmmm... now I'm confused.

Reports a list of all possible LiveCode script execution errors.

It's just a return-delimited list of LC errors, whose line number corresponds to the error number. In itself it catches nothing, it's just a a verbose dictionary. So why should it not be in standalones

Also - when the time time I included this in a standalone for distribution, it kept firing with either numbers or nothing and was always non-fatal - users just dismissed it and I just shrugged my shoulders