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 -- Gabriel Roldán ([EMAIL PROTECTED]) Axios Engineering (http://www.axios.es) Tel. +34 944 41 63 84 Fax. +34 944 41 64 90 ------------------------------------------------------------------------- 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
