#203 closed defect (fixed)
Iterator bugs in the collection package
Reported by: | james dot talmage at jrtechnical dot com | Owned by: | |
---|---|---|---|
Priority: | high | Milestone: | |
Component: | Core | Version: | 0.1 |
Keywords: | Cc: | ||
Blocked By: | Blocking: |
Description
Detailed description found in this thread at Dojo-Interest http://article.gmane.org/gmane.comp.web.dojo.user/1800
Change History (3)
comment:1 Changed 15 years ago by
Milestone: | → 0.3release |
---|---|
Priority: | high → normal |
severity: | critical → normal |
comment:2 Changed 15 years ago by
Resolution: | → fixed |
---|---|
Status: | new → closed |
This is fixed. We're supporting three forms of iteration:
(where iter == an iterator instance)
for (; !iter.atEnd; iter.moveNext()){ } do { } while (iter.moveNext()); while (!iter.atEnd){ }
Note that this fix immediately populates iterator.current with the *first* member of the collection being iterated, as opposed to starting with a null member. This means you *cannot* use "while (iter.moveNext())" without realizing that by doing that, you are starting with a 1-based index system (as opposed to a zero-based system).
Note: See
TracTickets for help on using
tickets.
I have a hard time rating this a either "critical" or high-priority since we've never shipped this API as part of a release.