W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2012

[whatwg] Endianness of typed arrays

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 28 Mar 2012 03:06:27 -0700
Message-ID: <4F72E2A3.5090504@mit.edu>
On 3/28/12 3:01 AM, Mark Callow wrote:
> So now you are saying that only the JS-visible state of ArrayBuffer is
> little-endian.

The JS-visible state of conversions from multi-byte-sized quantities to 
bytes or back is little-endian.

> The JS-visible state of int32Array, etc. is in
> platform-endiannesss.

I'm not even sure what that would mean.  The JS-visible state of an 
Int32Array is a sequence of 32-bit integers.  It doesn't make sense to 
talk about its endianness until the underlying bytes are examined in 
some way (e.g. by creating a view of some other type for the underlying 
array buffer).

-Boris
Received on Wednesday, 28 March 2012 03:06:27 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:40 UTC