We're getting feedback on TypedArrays from other listservs. This is
good; the conversation about Typed Arrays may be best served outside of
Khronos as well :)
-------- Original Message --------
I'm surprised no one has said this yet but here goes:
ArrayBuffer needs to extend Array. In other words instances of
ArrayBuffer needs to also be instances of Array
var ab = new ArrayBuffer;
assert(ab instanceof ArrayBuffer);
assert(ab instanceof Array);
You will also need to make sure that all the internal methods are
defined. See 8.12 Algorithms for Object Internal Methods of ES5. For
example what does it mean to do [[Delete]] on a byte array?
On Thu, May 13, 2010 at 05:57, Arun Ranganathan <firstname.lastname@example.org> wrote:
> Greetings, TC-39 WG and script mavens!
> Browser vendors participating in the WebGL WG intend to implement the "Typed
> Arrays" specification, allowing for greater manipulation of binary data:
> The draft specification (a work in progress) resides at Khronos, which is
> typically an unusual home for something integral to the rest of the web
> platform. Khronos is where we work on WebGL, which enjoys Google, Opera,
> Mozilla, and Apple participation, amongst other organizations.
> The general usefulness of constructs such as ArrayBuffers (covered in the
> "Typed Arrays" draft specification) lends itself to other web platform
> specifications, such as the File API, parts of which are implemented in
> Firefox 3.6.3:
> In the above draft (also a work in progress), the Blob interface exposes an
> ArrayBuffer property, which can then be used with different views.
> While implementations are currently proceeding unimpeded by standards-track
> considerations, it would be useful if Typed Arrays were taken on as a work
> elsewhere, and if so, where?
> -- A*
> es-discuss mailing list