+1.

I don't really see the point of the asMapEntry() method either. If someone wants the entries, they could just do it the old fashioned way [Map.entrySet().iterator()].




Stephen Colebourne wrote:
The MapIterator interface has an asMapEntry() method that gets the current
element at the iterator as a Map Entry.

The interface desires that the MapEntry returned is connected to the map,
such that changes made to setValue affect the map. This can be difficult to
implement, and if used would probably mess up the iterator.

How useful is the asMapEntry() method? I'm planning to remove it if no one
objects :-)

Stephen


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to