aaime++ I imagine the "removal of useless generics from GeoAPI" will be the valuable contribution GeoTools makes when we switch to Java 5. > Martin Desruisseaux ha scritto: > >> Things may become easier when Geotools will be allowed to target Java >> 5: Javadoc >> will work with the same JDK, the "unsupported/geometry" module will >> become an >> ordinary module (no more "enable on Java 5" profile hack) and we will >> not need >> anymore the "geoapi-nogenerics" hack. I really miss generic types, >> and my code >> has many "todo: uncomment when we will be allowed to compile for J2SE >> 1.5". >> Carrying Java 1.4 compatibility is becoming heavier and heavier... > Agreed. At the same time, I fear the day we'll switch to java 5 > precisely because of generics. Light usage of generics is intuitive, > makes things explicit, and so on (think using typed collections). > Same goes for autoboxing. > > But if you get overboard and start using more obscure features, the > incomplete generic implemetation in java will bite you, as proved > by numerous blogs on generic usage issues on the web (just do a search > with "java generics issues" on Google and you'll have you hands plenty). > > And I know we have a strong tendency to go overboard and get fancy. > So, I wait for the java5 changes wave with much concern. > Cheers > Andrea
------------------------------------------------------------------------- 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
