On 7/18/13 4:55 PM, Bill McCloskey wrote:
Could you elaborate on the problem a little more? Is Servo creating its own proxy handlers
Presumably yes, just like Gecko is right now. Basically one proxy handler per WebIDL interface that has proxy-like behavior.
We already have three reserved slots available for proxy handlers to use. Is that not enough?
What servo is trying to do is what you were proposing at some point for Gecko: using the JS heap for all DOM objects, and storing their members in reserved slots.
So three reserved slots are not enough to the extent that DOM objects have more than three members (and they do!).
This sounds like a major change to the engine.
To some extent, yes. It's not exactly the first major change we've made to play nicer with the DOM, and I expect it won't be the last for Servo..
Or would there be some kind of macro system to generate them statically for each handler?
The current approach is compile-time (C++ or Rust compile time) code generation that generates static JSClasses and handler implementations.
-Boris _______________________________________________ dev-tech-js-engine-internals mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
