I am going to just do a quick status update as I wait for a build. Graham and I have been working on unsupported/geometry in earnest and are finding it a little slow going. Writing test cases is hard due to two reasons: 1) many constructs do not have equals/hashcode defined (CurveImpl etc...) - code that tests DirectPosition equality using equals is currently using the default Object.equals implementation - so we are unsure where == is intended and where equals is intended - code that test equality is running into the same problem as with JTS - geometry.equals( geometry2 ) is different from geometry.equals( (Object) geometry) - and so on ... basically tests are hard to write right now and GeoAPI gives little guidance at this time
2) some constructors may attempt simplification (rather then just doing what they are told) - This seems to be the case with constructing a Ring (an attempt is made to simplify the curve) - On a related note Eclipse does a great job of generating equals and hashcode (much better then me actually). Cheers, Jody ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
