W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2009

Re: [webidl] DOMString

From: Cameron McCormack <cam@mcc.id.au>
Date: Wed, 22 Apr 2009 13:30:44 +1000
To: Oliver Hunt <oliver@apple.com>
Cc: WebApps WG <public-webapps@w3.org>
Message-ID: <20090422033044.GE16598@arc.mcc.id.au>
Cameron McCormack:
> > Seems reasonable to state that. I’ve added a note to do that when
> > I get some time to allocate to editing Web IDL again.

Oliver Hunt:
> I actually thought about this some more, and realised i'm not entirely  
> sure this should be part of webidl as it seems a little too language  
> specific.  Eg. WebKit also provides an objective-c interface to the DOM 
> to application developers, allowing them to interact with a webpage (or 
> other content) through the DOM directly from their application code.

It’s only the ECMAScript language binding that uses the ES ToString etc.
algorithms, so I think it would be fine to define in the ES language
binding section that exceptions thrown when converting an IDL value to
an ECMAScript value or vice versa will propagate to whatever invoked
that conversion.

We could certainly add similar language for the Java language binding
section too, though I think there’s less scope for those conversions to
throw exceptions (maybe ones like OutOfMemoryException).  I agree that
exception propagation behaviour is going to be somewhat language
specific, since some language bindings may not even have exceptions as
part of the language, so I think that means that it should be defined
separately for each language.

Until (unless) somebody writes up a Web IDL language binding for
Objective-C, the best you can hope for is for Obj-C implementations to
do something “sensible”.

-- 
Cameron McCormack ≝ http://mcc.id.au/
Received on Wednesday, 22 April 2009 03:31:25 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:31 GMT