On 9/14/19 4:38 PM, David Teller wrote:
Does this have any impact on SpiderMonkey error handling?
It does not; this is purely about errors thrown through bindings or other ErrorResult consumers in Gecko.
In SpiderMonkey, errors are typically thrown via the (JS_)ReportErrorNumber* APIs or via (JS_)ReportError*. The latter just take a string (and possibly some substitutions); the former _can_ lead to very generic error messages if people just use a single error number in too wide a set of cases, but usually SpiderMonkey is pretty good about not doing that.
In particular, there is no SpiderMonkey equivalent for "default message that goes with a given error type" like DOMException has, so whenever you throw an exception you end up thinking at least a little about what the message should be.
-Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
