Closed
Bug 7795
Opened 26 years ago
Closed 8 years ago
exorcise nsIEnumerator in favor of nsISimpleEnumerator
Categories
(Core :: XPCOM, defect, P3)
Core
XPCOM
Tracking
()
RESOLVED
FIXED
People
(Reporter: waterson, Assigned: erahm)
References
()
Details
(Keywords: arch)
...or some other more scripable interface.
I've started on this crusade several times only to be chopped at the knees by
lethargy or some other overwhelming circumstance.
Reporter | ||
Comment 2•25 years ago
|
||
Moving out non-critical tasks.
Comment 4•25 years ago
|
||
In verifying bug 8790, I just wanted to point out that warren mentioned cleaning
up nsIBidirectionalEnumerator also... Including his original comment:
"Chris -- you started this, so I'll help you finish it. :-)
We should eradicate nsIEnumerator and nsIBidirectionalEnumerator from
throughout the codebase if we can, switching over to nsISimpleEnumerator.
Having both is bad because they're incompatible.
We probably should remove the class definitions from nsEnumeratorUtils.h and
replace them with function calls.
When we're done, we can rename nsISimpleEnumerator to nsIEnumerator too."
Comment 6•25 years ago
|
||
In fact, I'd like to use the even better enumerators where possible, i.e., |
nsIInputIterator|, |nsIOutputIterator|, |nsIForwardIterator|, |
nsIBidirectionalIterator|, |nsIRandomAccessIterator|, which will provide easy
access to the |nsISimpleEnumerator| functionality that JS clients in particular
still love
Assignee: waterson → scc
Status: ASSIGNED → NEW
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 7•25 years ago
|
||
mass re-assigning to my new bugzilla account
Assignee: scc → scc
Status: ASSIGNED → NEW
Updated•25 years ago
|
Status: NEW → ASSIGNED
Comment 8•22 years ago
|
||
I guess we missed the boat on these (by about a hemisphere). Our collection
classes are pretty much frozen across the board; I don't see any realistic mass
resolution to this situation before 2.0.
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WONTFIX
Should this be closed just because this didn't make 2.0?
The nsIEnumerator is still declared obsolete so this work should be done some day. I've not found any other bug for this.
https://developer.mozilla.org/en-US/docs/XPCOM_array_guide
Status: RESOLVED → REOPENED
OS: Windows NT → All
Hardware: x86 → All
Resolution: WONTFIX → ---
Updated•8 years ago
|
Depends on: nuke-nsSupportsArray
Assignee | ||
Updated•8 years ago
|
Status: REOPENED → RESOLVED
Closed: 22 years ago → 8 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•