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

[Bug 16767] Allow user objects for Array[] types

From: <bugzilla@jessica.w3.org>
Date: Mon, 10 Dec 2012 06:57:09 +0000
To: public-script-coord@w3.org
Message-ID: <bug-16767-3890-TJYbnWZeGD@http.www.w3.org/Bugs/Public/>

--- Comment #15 from Cameron McCormack <cam@mcc.id.au> ---
(In reply to comment #14)
> I'm not sure that works.  Specifically, non-callback interfaces and
> sequences are currently distinguishable.  But as the overload resolution
> algorithm is written, if I have this IDL
>   void foo(long arg);
>   void foo(sequence<long> arg);
> and I pass in a platform object that's not a platform array object, it won't
> pick up the second overload, because it fails the "any other type of object"
> test as far as I can tell...

You're right that "any other type object" wording is troublesome; I too eagerly
merged some of the steps in there.  I think we still want platform objects that
support indexed properties to be able to be passed as sequence<T> types.

How about this:


Note that this continues to disallow native Array objects from being passed as
dictionary, callback interface and callback function values.

You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 10 December 2012 06:59:34 UTC

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