On Fri, Jun 29, 2012 at 9:50 AM, Boris Zbarsky wrote:
> On 6/29/12 12:25 PM, Joshua Bell wrote:
>
>> void f(float[] x); // overload A
>> void f(DOMString x); // overload B
>>
>> WebIDL itself, of course, doesn't dictate how matching and dispatching
>> should be implemented
>>
>
> Actually, it doe
On Fri, Jun 29, 2012 at 9:51 AM, Boris Zbarsky wrote:
> On 6/29/12 12:37 PM, Kyle Huey wrote:
>
>> #5. Neither T[] nor DOMString admits null as a value.
>>
>
> DOMString does not admit null as an IDL value.
>
> Which means that ES null is stringified when converting to DOMString.
>
> -Boris
>
>
On 6/29/12 12:37 PM, Kyle Huey wrote:
#5. Neither T[] nor DOMString admits null as a value.
DOMString does not admit null as an IDL value.
Which means that ES null is stringified when converting to DOMString.
-Boris
On 6/29/12 12:25 PM, Joshua Bell wrote:
void f(float[] x); // overload A
void f(DOMString x); // overload B
WebIDL itself, of course, doesn't dictate how matching and dispatching
should be implemented
Actually, it does.
http://dev.w3.org/2006/webapi/WebIDL/#dfn-overload-resolution-algorithm
On Fri, Jun 29, 2012 at 9:25 AM, Joshua Bell wrote:
> Over in WebKit-land there's some disagreement about WebIDL method overload
> resolution, specifically around passing null, arrays (T[]) and the concept
> of Nullable.
>
> Here's an example where we're just not sure what the WebIDL spec dictate
Over in WebKit-land there's some disagreement about WebIDL method overload
resolution, specifically around passing null, arrays (T[]) and the concept
of Nullable.
Here's an example where we're just not sure what the WebIDL spec dictates:
void f(float[] x); // overload A
void f(DOMString x); // ov
