Re: Observability of NaN distinctions — is this a concern?
allen at wirfs-brock.com
Mon Mar 25 16:20:05 PDT 2013
On Mar 25, 2013, at 4:05 PM, Brendan Eich wrote:
> Allen Wirfs-Brock wrote:
>> BTW, isn't cannonicalization of endian-ness for both integers and floats a bigger interop issue than NaN cannonicalization? I know this was discussed in the past, but it doesn't seem to be covered in the latest Khronos spec. Was there ever a resolution as to whether or not TypedArray [[Set]] operations need to use a cannonical endian-ness?
> Search for "byte order" at https://www.khronos.org/registry/typedarray/specs/latest/.
I had already search for "endian" with similar results. It says that the default for DataViews gets/sets that do not specify a byte order is big-endean. It doesn't say anything (that I can find) about such accesses on TypedArray gets/sets.
More information about the es-discuss