Jesse Eichar wrote:
I agree with you for the most part Martin. But if you look at some
implementations of equals, such as java.util.AbstractList, you will
find that it checks only that the object implements the interface and
only uses public methods to determine equality. Because only the
interface methods are used we don't have to worry about symmetry
violations. You get into trouble when you start casting to particular
implementations.
I think the equals(and hashcode) methods should be fixed.
Agreed - we went through this pain w/ FeatureType & Feature,
sure hope this cleanup will pay off in the end.
Jody
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
