[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Public WebGL] Should GLfloat and GLclampf be typedefs for "unrestricted float"?

I don't think it should throw. It should just pass them on.

On Mon, Nov 19, 2012 at 10:41 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

On 11/19/12 8:33 AM, Florian Bösch wrote:
Note that the ES 2.0 specifications clamping behavior is modified by
http://www.khronos.org/registry/gles/extensions/EXT/EXT_color_buffer_half_float.txt in
that output, blend and clear clamps are removed when the target is
floating point.

I'm not sure how relevant this is to my question...  The question, in case it wasn't clear, is whether passing Infinity, -Infinity, and NaN to various floating-point things in WebGL should throw at the binding level or whether it should pass through the argument as-is to the underlying WebGL implementation (which could then still choose to throw, if the throwing behavior needs to be conditional on something like which extensions are in use).


You are currently subscribed to public_webgl@khronos.org.
To unsubscribe, send an email to majordomo@khronos.org with
the following command in the body of your email:
unsubscribe public_webgl