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

Re: [Public WebGL] Requirements for bufferData don't make sense given the IDL




On 4/2/12 6:29 PM, Glenn Maynard wrote:
On Mon, Apr 2, 2012 at 9:22 AM, Boris Zbarsky <bzbarsky@mit.edu
<mailto:bzbarsky@mit.edu>> wrote:


In particular, it says:

      If the passed data is null then an INVALID_VALUE error is generated.

    But the IDL declarations for this method don't allow |data| to be
    null; an attempt to pass null will throw during the WebIDL overload
    resolution algorithm.  Was this requirement meant to be on
    bufferSubData (which does allow null to be passed)?  Or is
    bufferData supposed to have an overload that allows null?


Until recently, there were no nullable declarations in the spec at all. Some were added recently, and this is still being ironed out; this may be part of that. See https://www.khronos.org/webgl/public-mailing-list/archives/1203/msg00084.html. (https://www.khronos.org/webgl/public-mailing-list/archives/1203/msg00086.html is also relevant; it's an attempt to remove the need for some functions to be nullable.)

That's great as history goes; it doesn't resolve the issue.

-Boris


----------------------------------------------------------- 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 -----------------------------------------------------------