Closed
Bug 577638
Opened 14 years ago
Closed 14 years ago
Outdated comments in XPCOMUtils.jsm after Bug 568691
Categories
(Core :: XPConnect, defect)
Core
XPConnect
Tracking
()
RESOLVED
FIXED
People
(Reporter: me, Unassigned)
References
Details
As I understand it (which is not particularly well so this might be INVALID) Bug 568691 removed the ability of XPCOMUtils.jsm to register entries with the category manager. However the comments in XPCOMUtils.jsm still describe the unused _xpcom_categories object. It's only mentioned in a couple of places now, two comments, one extension (that presumably retains it for backwards compatibility?) and one other place that I'm not sure about: http://mxr.mozilla.org/mozilla-central/search?string=_xpcom_categories
Comment 1•14 years ago
|
||
https://developer.mozilla.org/en/XPCOM/XPCOM_changes_in_Gecko_2.0#Category_registration seems to agree. While we're there, step 3 in the XPCOMUtils comment still talks about NSGetModule and should be updated too. http://mxr.mozilla.org/mozilla-central/source/js/src/xpconnect/loader/XPCOMUtils.jsm#98
Blocks: data-driven-compreg
Comment 2•14 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/46973bbe4ef9
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
(In reply to comment #2) > http://hg.mozilla.org/mozilla-central/rev/46973bbe4ef9 I notice that _xpcom_categories wasn't removed from the comment, not sure if that was deliberate or an oversight.
Comment 4•14 years ago
|
||
It's in the "The following properties were used prior to Mozilla 2" section, so the comment is correct, no?
(In reply to comment #4) > It's in the "The following properties were used prior to Mozilla 2" section, so > the comment is correct, no? Ok, I intepreted it as a separate section but now you say that it makes sense, thanks.
You need to log in
before you can comment on or make changes to this bug.
Description
•