This is just false. There is absolutely nothing wrong with a getClass() != o.getClass() based equals method. It is 100% consistent, transitive, symmetric, and reflexive. It does, however, trip up certain JPA implementations. Which my OP tries to fix.
Your idea is a massive undertaking, requiring changes to virtually 100% of all existing java code. That's a few billion lines. It's never going to happen. On Oct 17, 11:56 am, Miroslav Pokorny <miroslav.poko...@gmail.com> wrote: > im not suggesting that any interface be amended - im just saying instead of > delegating to classes Object.equals(Object) wrap tests with extra tests if > either implement CanEquals(Object). In the end whole idea is broken because > you can never do the right thing and some hidden wrong action is just going > to screw someone up. If people want proper equals/hashcoding they can design > the class hierarchies properly and do the equals and hashcodes properly. -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to javapo...@googlegroups.com. To unsubscribe from this group, send email to javaposse+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
