> - 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 the typed arrays and the hope there is that Waldo's meta-object protocol refactoring will let us handle typed arrays as native objects with a special ElementsHeader (which will be necessary to allow storing named own properties on typed arrays which, last I heard, is proposed for the spec and we don't (and can't, without doing another one of these 'delegate objects', easily) do). 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). Cheers, Luke _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
