I have brought this up before as well. Martin brought up a good point in that unless the interface explicitly states what makes implementations equal to one another, it is open to interpretation and best to just compare based on implementation.
-Justin Gabriel Roldán wrote: > Hi all, > > are the Filter and Expression implementations meant to properly implement > equals and hashcode? > If so, we are in trouble, as (almost?)none of the FunctionExpression > implementations does. > > For the ones that do, should we move to comparisons based on the geoapi > interfaces rather than on concrete implementation? I know the geoapi > interfaces don't impose interface based comparisons. Should they? > I know this way is harder to achieve symmetry, so I'd like to know if there > already is an agreed position on the topic, or there is place to go the java > Collections way > > just curious. > > Gabriel > -- Justin Deoliveira [EMAIL PROTECTED] The Open Planning Project http://topp.openplans.org ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
