[Public WebGL] Oversight in bufferData and bufferSubData specification

Glenn Maynard [email protected]
Sat May 21 01:25:31 PDT 2011

On Sat, May 21, 2011 at 3:31 AM, Cedric Vivier <[email protected]> wrote:
> How about rather specifying that an INVALID_OPERATION is generated
> when passing a Float64Array ?
> We already do that kind of check with texImage2D if the
> ArrayBufferView type does not correspond with the format.
> This would keep the IDL lighter and allow extensions to use Float64
> buffers with the same API instead of having to declare their own.

That's consistent with how texture format extensions work, too:
OES_texture_float doesn't expose new entry points, it just causes
existing ones to no longer fail for certain argument types.

Doing it at the IDL level isn't compatible with texImage2D's complex
constraints, either ("buffer type must match the specified type").
bufferData doesn't have this problem, but only doing it there doesn't
seem worth the inconsistency...

Glenn Maynard
You are currently subscribed to [email protected]
To unsubscribe, send an email to [email protected] with
the following command in the body of your email:
unsubscribe public_webgl

More information about the public_webgl mailing list