Closed
Bug 791322
Opened 12 years ago
Closed 12 years ago
GC: Unexport Rooted classes that are not part of the public API
Categories
(Core :: JavaScript Engine, defect)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
mozilla18
People
(Reporter: terrence, Assigned: terrence)
References
Details
(Whiteboard: [js:t])
Attachments
(1 file, 2 obsolete files)
126.76 KB,
patch
|
billm
:
review+
|
Details | Diff | Splinter Review |
The fact that these are exposed has allowed us to be somewhat sloppy with what gets used in publicly exported headers. This also has the potential to be majorly troublesome down the road. Lets put the cat back in the bag before things get seriously messy.
Attachment #661287 -
Flags: review?(wmccloskey)
Assignee | ||
Comment 1•12 years ago
|
||
Comment on attachment 661287 [details] [diff] [review]
v0
Okay, this is going to take some more hacking: I shouldn't have just assumed that Rooted isn't already used all over the browser. New patch in a bit.
Attachment #661287 -
Attachment is obsolete: true
Attachment #661287 -
Flags: review?(wmccloskey)
Assignee | ||
Comment 2•12 years ago
|
||
The browser builds locally and a try run is up at:
https://tbpl.mozilla.org/?tree=Try&rev=e9eef8698885
Attachment #661430 -
Flags: review?(wmccloskey)
Comment on attachment 661430 [details] [diff] [review]
v1: The cat is back in the bag.
Review of attachment 661430 [details] [diff] [review]:
-----------------------------------------------------------------
The good thing about this patch is that it hides Rooted from the API, which we're not sure we want exposed. The bad thing is that, to satisfy the compiler, it adds fromMarkedLocation in 20 places that are not guaranteed to be marked. That seems likely to really confuse people. Overall, I think we're better off sticking with the status quo. It's possible that people will add Rooted in more places, but it will be easy to fix those when we have a coherent strategy.
Attachment #661430 -
Flags: review?(wmccloskey)
Assignee | ||
Comment 4•12 years ago
|
||
Perhaps it would make more sense to move Rooted from JS:: to js:: to better signal our intent?
Yeah, I think that would be a good idea.
Assignee | ||
Comment 6•12 years ago
|
||
The browser and jsapi files were changed with a sed script. Try run up at:
https://tbpl.mozilla.org/?tree=Try&rev=1b59c7fcb34e
Attachment #661430 -
Attachment is obsolete: true
Attachment #664308 -
Flags: review?(wmccloskey)
Attachment #664308 -
Flags: review?(wmccloskey) → review+
Assignee | ||
Comment 7•12 years ago
|
||
Green try run at:
https://tbpl.mozilla.org/?tree=Try&rev=1b59c7fcb34e
Pushed at:
https://hg.mozilla.org/integration/mozilla-inbound/rev/b9721197c221
Comment 8•12 years ago
|
||
Status: ASSIGNED → RESOLVED
Closed: 12 years ago
Flags: in-testsuite-
Resolution: --- → FIXED
Target Milestone: --- → mozilla18
You need to log in
before you can comment on or make changes to this bug.
Description
•