Hi Oliver.
Oliver Hunt:
Conceivably the language could be a relatively simple and broad
statement along the lines of:
Any type conversions needed for a language binding should occur before
an API function is called, if a type conversion fails for any reason the
call should be aborted
Anne van Kesteren:
If something takes a DOMString as value is it clearly defined what
happens if the toString algorithm throws or returns a non-DOMString? I
haven't been able to find descriptions for that in the Web IDL
specification. E.g.
obj = { toString:function() { throw(haha) } }
On Tue, Apr 21, 2009 at 8:30 PM, Cameron McCormack c...@mcc.id.au wrote:
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
Hi Garrett.
Cameron McCormack:
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).
Garrett Smith:
I'm not sure, but I think you might have
Conceivably the language could be a relatively simple and broad
statement along the lines of:
Any type conversions needed for a language binding should occur
before an API function is called, if a type conversion fails for any
reason the call should be aborted
However this doesn't address
If something takes a DOMString as value is it clearly defined what happens
if the toString algorithm throws or returns a non-DOMString? I haven't
been able to find descriptions for that in the Web IDL specification. E.g.
obj = { toString:function() { throw(haha) } }
obj2 = {
On Apr 21, 2009, at 1:38 AM, Anne van Kesteren wrote:
If something takes a DOMString as value is it clearly defined what
happens if the toString algorithm throws or returns a non-DOMString?
I haven't been able to find descriptions for that in the Web IDL
specification. E.g.
obj = {
Anne van Kesteren:
If something takes a DOMString as value is it clearly defined what
happens if the toString algorithm throws or returns a non-DOMString?
Oliver Hunt:
I would assume that the exception will be propagated to the runtime, but
it should be stated.
Seems reasonable to state
On Apr 21, 2009, at 6:08 PM, Cameron McCormack wrote:
Anne van Kesteren:
If something takes a DOMString as value is it clearly defined what
happens if the toString algorithm throws or returns a non-DOMString?
Oliver Hunt:
I would assume that the exception will be propagated to the
runtime,
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
10 matches
Mail list logo
