Giovanni Campagna:
> Only one comment:
> it should be noted that with
> interface Example {
> sequence 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 preven
Only one comment:
it should be noted that with
interface Example {
sequence 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
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