> Extending AbstractMap is not the right way to add an equals, > hashcode and > toString method. I just committed real implementations for > the methods.
Was there something wrong with AbstractMap's implementations, or did you just want to keep SequencedHashMap's superclass as Object? I'm just wondering if there's something my unit tests aren't catching... -Paul -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
