> >Once we did get to this proxy = non-native state, I think we could simplify
> >the world a lot; e.g., removing ObjectOps and making js::Class store a
> >BaseProxyHandler* directly (NULL for non-proxies).
>
> How would removing ObjectOps work? Plenty of native types have custom
> versions of so
On Thu, Jul 25, 2013 at 7:11 AM, Luke Wagner wrote:
>
> IIRC, since the dawn of proxies, one of the goals was for "proxy" to
> eventually be synonymous with "non-native object".
That's very helpful from a high-level view. Thanks!
>Once we did get to this proxy = non-native state, I think we co
> That's basically my proposal in the earlier "allowing proxy objects to
> have extra reserved slots" thread, right? Is it really blocked on
> making typed arrays native?
I'll have to admit I didn't read that thread. I haven't thought through all
the details, but 'yes' it does seem possible.
__
On 7/25/13 7:11 AM, Luke Wagner wrote:
making js::Class store a BaseProxyHandler* directly (NULL for non-proxies).
That's basically my proposal in the earlier "allowing proxy objects to
have extra reserved slots" thread, right? Is it really blocked on
making typed arrays native?
-Boris
__
> - The only examples of non-native objects in SM are ObjectProxy,
> OuterWindowProxy, FunctionProxy, ArrayBuffer, and the typed arrays
> (Int8Array, etc).
IIRC, since the dawn of proxies, one of the goals was for "proxy" to eventually
be synonymous with "non-native object". The main outlier is
On Wed, Jul 24, 2013 at 9:19 PM, Nicholas Nethercote
wrote:
>
> "what exactly is a native object"?
sfink wrote about this in
https://bugzilla.mozilla.org/show_bug.cgi?id=896759#c2. I've quoted
it below.
Nick
In my mind, isNative()'s meaning is a gooey gob of stuff, one piece of
which is "the
6 matches
Mail list logo
