JSObjectOps.setProto 编辑
Obsolete since JavaScript 1.8.5
This feature is obsolete. Although it may still work in some browsers, its use is discouraged since it could be removed at any time. Try to avoid using it.
Warning! JSObjectOps
is not a supported API. Details of the API may change from one release to the next. This documentation should be considered SpiderMonkey internals documentation, not API documentation. See bug 408416 for details.
The JSObjectOps.setProto
and setParent
callbacks implement the JS_SetPrototype
and JS_SetParent
functions. These callbacks share the same type, JSSetObjectSlotOp
.
Syntax
typedef JSBool (*JSSetObjectSlotOp)(JSContext *cx, JSObject *obj,
uint32 slot, JSObject *pobj);
Name | Type | Description |
---|---|---|
cx | JSContext * | Pointer to the JS context in which the object's prototype or parent is being modified. |
obj | JSObject * | The object whose prototype or parent is being modified. |
slot | uint32 | The index of the slot being modified: JSSLOT_PROTO for the JSObjectOps.setProto callback, and JSSLOT_PARENT for the JSObjectOps.setParent callback. |
pobj | JSObject * | The new prototype or parent object. |
Description
These hooks must check for cycles without deadlocking, and otherwise take special steps. See js_SetPrototype
or js_SetParent
in js/src/jsobj.c
for an example.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论