Open
Bug 992977
Opened 10 years ago
Updated 2 years ago
JS_DefineProperties incorrectly equates the absence of JSPROP_NATIVE_ACCESSORS with selfHosting
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
NEW
People
(Reporter: bholley, Unassigned)
Details
See http://mxr.mozilla.org/mozilla-central/source/js/src/jsapi.cpp#3196 JSPROP_NATIVE_ACCESSORS has historically meant that that the accessors are JSNatives, not JSPropertyOps. So If anyone was using JS_DefineProperties these days for JSPropertyOp-backed properties (which they apparently aren't), they'd hit the self-hosting branch and assert. So, do we want to go fix this? Or do we want to just declare victory and change the JSPropertySpec format to take JSNatives directly?
Reporter | ||
Updated•10 years ago
|
Flags: needinfo?(jorendorff)
Reporter | ||
Comment 1•10 years ago
|
||
Looks like Nathan introduced this in bug 958262.
Reporter | ||
Comment 2•10 years ago
|
||
And bug 958262 comment 8 implies that till was even aware of this?
Flags: needinfo?(till)
Comment 3•10 years ago
|
||
(In reply to Bobby Holley (:bholley) from comment #0) > So, do we want to go fix this? Or do we want to just declare victory and > change the JSPropertySpec format to take JSNatives directly? Uh... Declare victory, for sure. Is it really true no one is using that anymore? This seems too good to be true.
Flags: needinfo?(jorendorff)
Comment 4•10 years ago
|
||
Urgh, I somehow missed this needinfo :( And yes, declare victory, definitely. I don't know why I didn't see that this means that we can get rid of even more stuff, but it's very nice.
Flags: needinfo?(till)
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•