Closed Bug 569666 Opened 14 years ago Closed 14 years ago

global.ctypes shouldn't be enumerable

Categories

(Core :: js-ctypes, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
mozilla1.9.3a5

People

(Reporter: Waldo, Assigned: Waldo)

References

Details

(Whiteboard: fixed-in-tracemonkey)

Attachments

(1 file)

Attached patch PatchSplinter Review
None of the other global names are enumerable, it's odd man out, and it also happens to break uneval(global) right now in full-browser builds inside the JS shell.

Also, NULL getter/setter means use the object's class's getter/setter, which may be something awful -- not the easy, nice, traceable JS_PropertyStub.
Attachment #448805 - Flags: review?(jorendorff)
Attachment #448805 - Flags: review?(jorendorff) → review+
Comment on attachment 448805 [details] [diff] [review]
Patch

Right. This is the easiest way to recover the tests that have been failing ever since js-ctypes landed. We shouldn't have let them go this long.
I think there are other cases of NULL getter/setter where the class doesn't have anything interesting, in that file -- if you feel like it you could check those too :)
http://hg.mozilla.org/tracemonkey/rev/611696dd3663

Only fixing the one instance because it happened to be driveby -- others should be fixed, but aiming for the narrowest fix possible here rather than get bogged down in "irrelevancies".
Whiteboard: fixed-in-tracemonkey
Target Milestone: --- → mozilla1.9.3a5
http://hg.mozilla.org/mozilla-central/rev/611696dd3663
Status: ASSIGNED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: