W3C home > Mailing lists > Public > public-linked-json@w3.org > February 2012

Fwd: [respec] Removed support for exceptions

From: Gregg Kellogg <gregg@kellogg-assoc.com>
Date: Tue, 7 Feb 2012 12:59:04 -0500
To: Linked JSON <public-linked-json@w3.org>
Message-ID: <53CF7583-02DE-41E1-B190-A0C63E20E508@greggkellogg.net>
I notice from Robin's post that WebIDL no longer supports raises, getraises or setraises. We make use of this in the API. This seems to imply that WebIDL can't describe that methods can raise errors. Here's the related issue [1].


[1] https://www.w3.org/Bugs/Public/show_bug.cgi?id=13866

Begin forwarded message:

> From: Robin Berjon <robin@berjon.com>
> Subject: [respec] Removed support for exceptions
> Date: February 7, 2012 8:15:37 AM PST
> To: "spec-prod@w3.org Prod" <spec-prod@w3.org>
> Hi all,
> just a heads up to all of you: since WebIDL has pulled support for the likes of raises, getraises, and setraises, I've now matched that up in ReSpec and have pulled support for them. The way this works is that in order not to break existing drafts that use those, I just silently ignore them (they are parsed but no output is generated for them). The next step, in a decent amount of time, will be to start warning when they're present, so I recommend updating your drafts to remove them (since it's not valid WebIDL anyway, it's the right thing to do).
> -- 
> Robin Berjon - http://berjon.com/ - @robinberjon
Received on Tuesday, 7 February 2012 18:03:35 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:18:33 UTC