Fwd: [dojo-contributors] [feedback wanted] Preferred Iteration forms

Tom Trenka ttrenka at gmail.com
Wed Apr 12 14:43:04 EDT 2006


No, that's why I sent out the email first before trying to code it.  Anyone
else prefer next() over current()?

On 4/12/06, James Burke <jburke at dojotoolkit.org> wrote:
>
> On 4/12/06, Tom Trenka <ttrenka at gmail.com> wrote:
> [snip]
> > var it=col.getIterator();
> >
> > while(!it.atEnd()){
> >     var item=it.current();
> >     // do stuff
> >  }
> >
> > The idea here is that current() not only returns the current item, but
> also
> > advances the internal cursor to the next item in the
> collection.  atEnd()
> > should be obvious. I will also provide an "item" property, which will be
> the
> > current item in the collection. Hopefully this is the best comprimise I
> can
> > think of.  It should also be able to support a for form...
> >
> > for(it.current();!it.atEnd(); it.current()){
> >    // do stuff.
> > }
> >
>
> if current() does a next operation underneath, I would then prefer
> calling the method next(). To me current implies I can call it many
> times and get the same value (no cursor movement). But that may be my
> java experience coloring my perception. Please disregard if this falls
> into the holy war section.
>
> James
> _______________________________________________
> dojo-contributors mailing list
> dojo-contributors at dojotoolkit.org
> http://dojotoolkit.org/mailman/listinfo/dojo-contributors
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.dojotoolkit.org/pipermail/dojo-contributors/attachments/20060412/ad3b2a8d/attachment.htm 


More information about the dojo-contributors mailing list