638
edits
JavaScript:SpiderMonkey:GC Futures: Difference between revisions
→Plans
(→Plans) |
(→Plans) |
||
| Line 141: | Line 141: | ||
This won't work because I plan to implement MT objects using custom JSObjectOps. So JS_AUTO_MT_OBJECTS would make all objects non-native, which would break major engine invariants (e.g. the global object must be native). | This won't work because I plan to implement MT objects using custom JSObjectOps. So JS_AUTO_MT_OBJECTS would make all objects non-native, which would break major engine invariants (e.g. the global object must be native). | ||
--> | --> | ||
=== Compartments and wrappers - internal details === | |||
A context is always "running in" a given compartment, normally the compartment of JS_GetScopeChain(cx). So, for example, <code>js_Atomize(cx, name, strlen(name), 0)</code> allocates the new string in whatever compartment cx is in. | |||
A consequence of this is that the API function <code>JS_SetProperty(cx, obj, name, vp)</code> must put cx into obj's compartment before calling <code>js_Atomize</code>. | |||