W3C home > Mailing lists > Public > public-script-coord@w3.org > April to June 2012

Re: [Public WebGL] Re: WebGL IDL for uniform1fv is not valid WebIDL

From: Glenn Maynard <glenn@zewt.org>
Date: Mon, 9 Apr 2012 17:25:36 -0500
Message-ID: <CABirCh_XAYUp9zzq-Oh1fDJ1tNC3tzrOuNQ-wdCMmASJZKUyGQ@mail.gmail.com>
To: Cameron McCormack <cam@mcc.id.au>
Cc: Boris Zbarsky <bzbarsky@mit.edu>, public webgl <public_webgl@khronos.org>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On Sun, Apr 8, 2012 at 7:52 PM, Cameron McCormack <cam@mcc.id.au> wrote:

> You're right about that btw; if an object implements an interface that
> supports indexed properties, then its [[GetOwnProperty]] internal method
> will never look at the prototype for array index properties, and you can
> also not create own array index properties on the object.  So I believe the
> optimisation that Glenn mentions is possible.  But I think the right thing
> here might be to make the changes to distinguishability to make this
> overloading valid.
>

It would be nice to be able to use JavaScript arrays and typed arrays
indistinguishably when calling native functions.  Rather than each API
defining separate entry points, having float[] imply that Float32Array is
allowed would help that, if that can be done in a way that doesn't make
implementing optimized versions for typed arrays hard.

That implies implementation work for any API taking numeric arrays.  I
don't know how many others exist that would be affected by that (if any).

-- 
Glenn Maynard
Received on Monday, 9 April 2012 22:26:05 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 May 2013 19:30:06 UTC