I am not sure I like backwards compatibility over consistency. Ie if we are going to break people let's at least do it with a usability goal in mind.
The other alternative is: GeoTools 2.5.x: - getRulesArray() - returns an array - getRules() - deprecated GeoTools 2.6.x - getRulesArray() - returns getRules().toArray( new Rule[0] ); - getRules() - return a List We sat through this change before in order to have a consistent use... Jody johann sorel wrote: > Hello, > > Proposal : http://docs.codehaus.org/display/GEOTOOLS/Upgrading+styles > > > We have a found a solution to upgrade GeoTools style interface without > breaking backward compatibility. > > The problem we had was "Array versus Collection" : > > -In GeoTools we have : Rule[] getRules(); > -In GeoAPI we have : List<Rule> getRules(); > (same thing for FeatureTypeStyles and Symbolizers) > > Seens both methods have the same signature we would break backward > compatibility. > > Here is the solution we applied : > Renaming GeoAPI method in : List<Rule> rules(); > > I will be on IRC meeting today if you have question. > If you have no objections please vote. > If you have objections please tell us what is the problem and we will > try to find a solution. > > > regards > > ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://sourceforge.net/services/buy/index.php _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
