"Alain Ravet" <[EMAIL PROTECTED]> wrote in message [EMAIL PROTECTED]">news:[EMAIL PROTECTED]... > Jacques Morel wrote: > > Why not all canonical methods (equals,hashCode,toString)? > > Because toString() is an exception : > it is frequent/not rare to overwrite it SOLELY to ease debugging sessions.
Except in cases of lazy API developers that instead of requiring getText() accessors use toString() on components. I have run across this sometimes in java APIs - some Swing components come to mind at the moment :-( As these classes are a minority I think this could be useful and catch possible errors. And, if implemented, I also think that optionally ignoring hashCode and equals would be useful and not to hard to include. Also methods chosen by the developer :-) I use an equalsImpl to resolve the problem of equals between classes and their sub-classes and would want to include this also. But we are going to far I think :-) Carlos -- Carlos Costa e Silva <[EMAIL PROTECTED]> _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://lists.jetbrains.com/mailman/listinfo/eap-features
