Spark Shen wrote:
But, do you agree to following RI on this strange behavior?
Personally, I think throw an IllegalStateException here is more
appropriate.
The spec for Iterator.remove() says:
"Throws ||IllegalStateException - if the next method has not yet been
called, or the remove method has already been called after the last call
to the next method."
So IMHO, it doesn't follow spec to throw IllegalStateException here, if
we think RI has bug here, the more careful solution is do nothing and
return.
Best regards
--
Paulex Yang
China Software Development Lab
IBM
---------------------------------------------------------------------
Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
