- From: Giovanni Campagna <scampa.giovanni@gmail.com>
- Date: Tue, 7 Jul 2009 12:21:58 +0200
- To: public-webapps@w3.org
Only one comment:
it should be noted that with
interface Example {
sequence<long> numbers;
}
In EcmaScript ex.numbers != ex.numbers, because each access to
"numbers" creates a new Array
This is probably counterintuitive to most users of the interface and
may prevent many uses of sequence<> as attributes (to avoid such
confusion).
Giovanni
2009/7/7 Cameron McCormack <cam@mcc.id.au>:
> Hello WG.
>
> I’ve finally fixed up sequences in Web IDL, and also added an array
> type. The difference is that:
>
> * sequences are effectively pass-by-value, represented by a JS Array
> or a Java array object, and
>
> * arrays are pass-by-reference, represented by a JS host object that
> acts similarly to an Array (including having Array.prototype in its
> prototype chain, but not supporting sparse arrays) or by a Java
> object that implements an interface defined in the spec that allows
> access to elements and the array length.
>
> JS Array objects can also be passed to host objects expecting an array,
> but the Array object will be converted into the special host object.
>
> http://dev.w3.org/2006/webapi/WebIDL/#idl-sequence
> http://dev.w3.org/2006/webapi/WebIDL/#idl-array
>
> http://dev.w3.org/2006/webapi/WebIDL/#es-sequence
> http://dev.w3.org/2006/webapi/WebIDL/#es-array
>
> http://dev.w3.org/2006/webapi/WebIDL/#java-sequence
> http://dev.w3.org/2006/webapi/WebIDL/#java-array
>
> Comments welcome.
>
> --
> Cameron McCormack ≝ http://mcc.id.au/
>
>
Received on Tuesday, 7 July 2009 10:22:38 UTC