It's not actually correct that they were introduced in LC8 -- the properties have been there since at least 6.0.1 ( https://github.com/livecode/livecode/blob/release-6.0.1/engine/src/lextable.cpp#L1343) and probably before.
Previously the home stack would set the custom property of the error stack on startup (using the engine properties), which to my mind is a slightly bizarre state of affairs and I'm not sure why it was done that way. On Fri, Oct 14, 2016 at 8:37 PM Devin Asay <devin_a...@byu.edu> wrote: > > > On Oct 14, 2016, at 1:24 PM, mwieder <ahsoftw...@sonic.net> wrote: > > > > Devin- > > > > Both the scriptExecutionErrors and scriptParsingErrors global properties > are > > currently undocumented. These contain the same lists that were formerly > > custom properties of card 1 of the error display stack. Both properties > were > > introduced for the LC8 series, and the custom properties were removed at > the > > same time. > > > > The global properties contain a cr-separated list of error descriptions > so > > that the numeric error value returned by the engine can be used as an > index > > to retrieve the text. > > > > Examples: > > get line 347 of the scriptExecutionErrors > > get line 61 of the scriptParsingErrors > > Thanks, Mark. Here’s my first draft. Suggestions appreciated and I can > modify it as needed. > > https://github.com/livecode/livecode/pull/4765 > > Devin > > > Devin Asay > Director > Office of Digital Humanities > Brigham Young University > > _______________________________________________ > use-livecode mailing list > firstname.lastname@example.org > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode _______________________________________________ use-livecode mailing list email@example.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode