Why two flavors of this method? Implementing equals() to return true across classes is indeed sometimes tricky or problematic, but here, seems exactly the right thing to do, for the same reason two Lists of different implementations can be equals().
On Thu, Jun 11, 2009 at 3:15 AM, Grant Ingersoll<gsing...@apache.org> wrote: > So, I think maybe instead of allowing equals() to return true across > implementations, we could add a static method that compares two Vectors and > returns true, something like: > > static boolean equivalent(Vector a, Vector b) > > > -Grant >
