On 8/29/22 16:11, Paul Dupuis via use-livecode wrote:
It could reduce a trouble should step to include the line numbers
programmatically in the error report.
No a huge priority in the scheme of things, but a "nice to have" sort of
thing. Does that answer the "why?"
Somewhat. If you already have the line number from the error message,
why not just grab that line of script? Or preface it with the line
number you already have in your possession?
But I find that the executionContexts gives me more information than
just where the error occurred, since the actual problem may be farther
up the line and it's only the end symptom that triggers the error.
use-livecode mailing list
Please visit this url to subscribe, unsubscribe and manage your subscription