Actually, using keysAndValuesDo: makes a lot of sense to me and seems to be a nice and clean way to resolve this discussion. I really like that it���s nicely polymorphic if we consider the keys of a sequenced collection to be the indexes. I just like this kind of simplicity ��� 

On Mar 18, 2015, at 18:55, Sean P. DeNigris <sean@clipperadams.com> wrote:

Lastly, apparently e.g. Dolphin has removed it completely in favor of #keysAndValuesDo: in response to a change in the ANSI standard. From http://forum.world.st/doWithIndex-tp3374968p3374975.html :
#doWithIndex: was in an early ANSI draft, presumably 
proposed by one of IBM's representatives but I can't really remember, and we 
had it in the version of Dolphin current at the time. Later it was removed 
from the standard and replaced with #keysAndValuesDo:, which makes sense 
since a sequenced collection can legimitately represent a "keyed collection" 
with integer keys. Therefore there is no need for a second enumerator that 
does the same thing but with key and value reversed.




---> Save our in-boxes! http://emailcharter.org <---

Johan Fabry   -   http://pleiad.cl/~jfabry
PLEIAD lab  -  Computer Science Department (DCC)  -  University of Chile