Opened 16 years ago

Closed 16 years ago

Last modified 15 years ago

#203 closed defect (fixed)

Iterator bugs in the collection package

Reported by: james dot talmage at jrtechnical dot com Owned by: [email protected]
Priority: high Milestone:
Component: Core Version: 0.1
Keywords: Cc:
Blocked By: Blocking:


Detailed description found in this thread at Dojo-Interest

Change History (3)

comment:1 Changed 16 years ago by alex

Milestone: 0.3release
Priority: highnormal
severity: criticalnormal

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.

comment:2 Changed 16 years ago by [email protected]

Resolution: fixed
Status: newclosed

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).

comment:3 Changed 15 years ago by (none)

Milestone: 0.3release

Milestone 0.3release deleted

Note: See TracTickets for help on using tickets.