W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2012

Re: Should Exceptions be Errors in the ECMAScript bindings?

From: Erik Arvidsson <arv@chromium.org>
Date: Fri, 22 Jun 2012 09:52:55 -0700
Message-ID: <CAJ8+Goi70e3FhZQy9huMKLKB+8TXA7CmDw4uGHUG4o=KwEHGGw@mail.gmail.com>
To: Allen Wirfs-Brock <allen@wirfs-brock.com>
Cc: Cameron McCormack <cam@mcc.id.au>, Travis Leithead <Travis.Leithead@microsoft.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Fri, Jun 22, 2012 at 8:40 AM, Allen Wirfs-Brock
<allen@wirfs-brock.com> wrote:
> Note that while there isn't currently any  special standardized behavior for
> Error, implementations do have non-standard behaviors such as capturing
> stack traces.  This would have to be dealt with in the actual
> implementations but conceptually is captured by the super constructor call.

For what it is worth DOMExceptions in WebKit (V8 and JSC) now have
Error.prototype on their prototype chain. I had to manually hook up
the stack property using the V8 embedding APIs (JSC adds stack to all
thrown objects).

Received on Friday, 22 June 2012 16:53:45 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:06 UTC