[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Typed Array spec updates: strawman proposals
- To: Kenneth Russell <email@example.com>
- Subject: Re: [Public WebGL] Typed Array spec updates: strawman proposals
- From: Ben Vanik <firstname.lastname@example.org>
- Date: Fri, 22 Apr 2011 21:23:55 -0700
- Cc: email@example.com
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-type; bh=N6UmMZC6SDp9TPcbBmGnhS/d5ptWdbBOp6g6cxywg18=; b=VAy7L+V4qbL7IgcsYxiM5gvwUHkHF9IE193VJVKx8TyVSxRvKaO8RqYZj4/qEd4nAk CdcWHS/Wt1QgSds4fQHmanyDBRIwVEfhkBb4EcIQLP6BcYA1qfp20LX5joZPyNGXmHf8 bTxp2yYMpbPw9zqP8YmASOVBJIy2Ndhpvvxmk=
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type; b=atJua3U7D3BoBwOSKj2Hfeqc/6iQUi9E9VgRo5917TuISul6SCReJcIrNtgjI5Ql7h aLXpSuMYJbPPLyU4Q+FHCePzOa8r9tAFKzxiSaKmQaC66VKY6dMqn6zLcQKE6VEW70JR 93VHO9kH1+vPzXc5yWK6CTxQslqOlaOL6tyhU=
- In-reply-to: <BANLkTimmJV8XCBAwD=sL=AvdhDStEB_8KQ@mail.gmail.com>
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- References: <BANLkTinB_LL6RSf4-kmS8SBp2tDgOuf_6Q@mail.gmail.com> <BANLkTimmJV8XCBAwD=sL=AvdhDStEB_8KQ@mail.gmail.com>
- Sender: firstname.lastname@example.org
It be useful to have an exception thrown on writes to closed arrays, just as exceptions are thrown on writes to read-only arrays.
If I were in a large, multi-threaded application and trying to debug flakiness it'd be a lot easier to identify write-after-postMessage cases as opposed to random code just not doing anything. I like setting all the sizes to zero, but on writes you'd get range exceptions and other things that aren't immediately traceable to the close action.
On Fri, Apr 22, 2011 at 7:22 PM, Ben Vanik <email@example.com>
Any reason that it's 'copyRange' instead of 'slice'? 'copyRange' is more explicit, but 'slice' is more consistent.
'isReadOnly' should probably be 'readOnly' (the name that is used elsewhere in the html spec, for example on the <input> element).
On Fri, Apr 22, 2011 at 6:20 PM, Kenneth Russell <firstname.lastname@example.org>
The Typed Array editors' draft has been updated:
with changes supporting the following functionality:
- Ability to copy sections of an ArrayBuffer
- Read-only ArrayBuffers
- Support for zero-copy data transfer via postMessage by defining the
behavior of ArrayBuffers and ArrayBufferViews under structured clone
The changes are clearly highlighted in the spec with "Strawman proposal".
The strawman proposal for the behavior of ArrayBuffers and views under
structured clone was discussed informally between Mozilla and Google,
and has undergone some iteration. (Earlier iterations involved making
an explicit API call to achieve transfer of ownership, and having the
default behavior perform a copy.) The current behavior was preferred
by members of the TC-39 committee, because it achieves unsurprising
We believe that these changes will be efficiently implementable in
Your feedback on these changes would be greatly appreciated. Please
send them to the list.
You are currently subscribed to email@example.com.
To unsubscribe, send an email to firstname.lastname@example.org with
the following command in the body of your email: