[Public WebGL] Should WebGLContextAttributes be a callback interface?

Boris Zbarsky [email protected]
Sun Apr 8 19:51:55 PDT 2012


On 4/8/12 10:49 PM, Cameron McCormack wrote:
> Any JS non-platform object can serve as a callback interface object.

Sure, but even then the "non-platform" restriction is kinda arbitrary.

> callback interface A {
> attribute long x;
> attribute long y;
> void f();
> };
>
> interface B {
> A g();
> };
>
> calling B.g() could return a new JS native object with "x", "y" and "f"
> properties.

Yep.  That's what it would do for a dictionary, right?  Or would it not?

> The same question arises with callback functions. If you defined
>
> callback SomeCallback = void ();
>
> interface C {
> attribute SomeCallback handler;
> };
>
> should C.handler be allowed to return a Function object that script
> didn't create? Maybe.

I wouldn't have a problem with that personally.

-Boris

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