Closed
Bug 11363
Opened 27 years ago
Closed 26 years ago
nsIEnumerator::IsDone semantics make scriptability awkward
Categories
(Core :: XPCOM, defect, P3)
Tracking
()
RESOLVED
WONTFIX
M11
People
(Reporter: rginda, Assigned: scc-obsolete)
Details
In nsIEnumerator.idl the IsDone method specifies no out param, and
(presumably... is this correct?) relies on the implementor to return
NS_ERROR_FAILURE to signify that the enumeration has reached an endpoint. This
would translate poorly if the interface were used from JavaScript. (ie. JS
would have to try { e.IsDone() } catch(){}, instead of do while (!e.IsDone()){}
|
||
Updated•27 years ago
|
Assignee: dp → scc
|
|
Assignee | |
Updated•27 years ago
|
Status: NEW → ASSIGNED
|
|
Assignee | |
Updated•27 years ago
|
Target Milestone: M10
|
|
Assignee | |
Updated•26 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 26 years ago
Resolution: --- → WONTFIX
|
|
Assignee | |
Comment 2•26 years ago
|
||
|nsIEnumerator| interface is deprecated. Now we use the |nsISimpleEnumerator|
interface which does not have this evil. Since |nsIEnumerator| is going away, we
don't need to fix this bug.
You need to log in
before you can comment on or make changes to this bug.
Description
•