2. What is a current situation about HashMap? Is the problem about
implementation or is there a plan to make a change in HashMap
interface?
java.util.HashMap?
Did you really mean HashMap?
Oops, I meant MultiMap.
-
To unsubscribe
other way to access
TODOs?
Takuya Murata
[EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
erator() and listIterator().
Having two classes for Iterator and ListIterator respectively is
straightforward than SingletonListIterator for both.
Anyway, I like SingleEntryCollection too. It is more general than
having classes for rather exceptionally
ter solution. Remember
adding things not only make things convenient but comes with cost of
maintenance, documentation and difficulty to comprehend.
Takuya Murata
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
this sounds hugely dangerous - the javadocs for List#equals(Object) for
example stipulate:
Compares the specified object with this list for equality. Returns
true if
and only if the specified object is also a list, both lists have the
same
size, and all corresponding pairs of elements in the two
On Wednesday, August 20, 2003, at 12:41 PM, Henri Yandell wrote:
On Wed, 20 Aug 2003, Takuya Murata wrote:
Yes, this is in line with your proposal; we can use
SingletonListIterator for both Iterator and ListIterator. I think the
problem of this solution is users probably expect
; we can use
SingletonListIterator for both Iterator and ListIterator. I think the
problem of this solution is users probably expect SingletonIterator
intuitively and might be puzzled why there is no such.
Takuya Murata
-
To
}
public ResetableListIterator singletonIterator () { ... }
}
It is possible to use just one concrete class for both methods above.
Given there is a few discussion of code review, I think every one is
busy maintaining the existing code base.
Takuya Murata
[EMAIL
