Andrea Aime wrote: > Why in the world GeographicBoundingBox.getXXXXBoundLongitude should > return a Double instead of a primitive, it just makes it harder to use > and generates more garbage?
In order to support incomplete metadata objects, we were given a choice between using null or Double.NaN. You are correct: it isn't pretty. For consistency, we chose to make all "double" instances into "Double" within the metadata package. We could, however, choose to be inconsistent -- and in this case, for instance, force the GeographicBoundingBox object to be null rather than its contents. Anyhow, this conversation should continue here: http://jira.codehaus.org/browse/GEO-103 Cory. ------------------------------------------------------------------------- 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 Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
