[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Public WebGL] Should texSubImage2D accept null like texImage2D does?
- To: Ms2ger <email@example.com>
- Subject: Re: [Public WebGL] Should texSubImage2D accept null like texImage2D does?
- From: Kenneth Russell <firstname.lastname@example.org>
- Date: Wed, 4 Apr 2012 18:49:38 -0700
- Cc: Tim Johansson <email@example.com>, Glenn Maynard <firstname.lastname@example.org>, Benoit Jacob <email@example.com>, public webgl <firstname.lastname@example.org>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:x-system-of-record; bh=aHnb+lsO0dQVZBnfDCUz1qrwp4kFmNcWR18glezKPrQ=; b=d8BXw3/uzbJrcgGIAZlyGs5dIf5L/UY22HrGM1pA9azzctMa8NVi/hBsGC36oaHPjS c6U3yIKvu4v5Gfk8O1YWOI8baX9PGAYwrsUl/u0oHiiUOAOwfltB+ePEhDfQk2QkvQzR H2n9PP3rfaR1cueJ6heU8XsPD88W6n9RoWGFZW56Sf9cZ7iyTEQZ9u6JbyKJuySp8a63 zHVUjR9cwBskj1Ja3baCzNy+2o/8cd6qNB7MDCb2Xn6ceckQ01HlLhaNPwKRffWqUBmT YUh5R740Ncvb5VEWCQkIt3vuncYqb/sCyu3MwW0Y/7m9hfNY6IEXSuP20F9FQjCIOwkd iB/w==
- In-reply-to: <4F606E6E.email@example.com>
- List-id: Public WebGL Mailing List <public_webgl.khronos.org>
- References: <1227138342.8279574.1331415408219.JavaMail.firstname.lastname@example.org> <1241945585.8279812.1331415744771.JavaMail.email@example.com> <CAMYvS2d14s7NvfdTqGFe0M9sGz2-u=iwwPG-ecthE-AGO1oDpg@mail.gmail.com> <4F5F2297.firstname.lastname@example.org> <CABirCh_d=WaeO2KP5EikC2JeGwevnZko358uOCmVf0ie7J3eOw@mail.gmail.com> <4F5F6EAB.email@example.com> <4F606E6E.firstname.lastname@example.org>
- Sender: email@example.com
On Wed, Mar 14, 2012 at 3:09 AM, Ms2ger <firstname.lastname@example.org> wrote:
> On 03/13/2012 04:58 PM, Tim Johansson wrote:
>> On 2012-03-13 15:37, Glenn Maynard wrote:
>>> On Tue, Mar 13, 2012 at 5:33 AM, Tim Johansson <email@example.com
>>> <mailto:firstname.lastname@example.org>> wrote:
>>> Yeah, if you leave the 6th parameter out it is tricky to tell if
>>> you tried to call the version taking 5 numbers and an object
>>> (HTMLImageElement) or the version taking 8 numbers and an object
>>> (TypedArray). In our implementation we would assume 0/null for the
>>> missing parameters and the call would match both versions. In that
>>> case we are highly likely to choose the one which does not cause
>>> an error.
>>> I think there has been quite a bit of work on this in WebIDL since
>>> we last looked at it, so it might actually be better specified
>>> now, but even if it is it would IMO mostly be a conformance test
>>> of WebIDL and not of WebGL.
>>> I'm not an expert on WebIDL, but this all looks tightly specified now.
>>> It's worth having a test for this in WebGL, since WebGL is exercising
>>> this part of WebIDL more than a lot of other current APIs.
>> Yeah, looks like it is well specified now. I don't have any strong
>> objections in this specific case right now (haven't checked if it is
>> implementable yet though) since IDL is a bit of a special case, but I
>> think we should be careful about testing other specs in the WebGL
>> conformance testsuite.
> The WebGL spec has a normative reference to WebIDL  (which incidentally
> claims to be referencing a September 2009 draft), so I would say that the
> WebGL test suite should test at least those parts of WebIDL that are relied
> upon in WebGL.
>  https://www.khronos.org/registry/webgl/specs/latest/#refsWEBIDL
Thanks, I've simply deleted the bogus date from the WebGL spec.
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: