Re: [Engine-devel] Use java.util.Collection where possible?

My two cents: There are two meanings of subtyping Collection (or any other interface, for that matter) - additional logic and specific implementation. I think wherever possible, we should use the interface that infers as much logic as possible (e.g., java.util.List for ordering, java.util.Set for uniquness, java.util.SortedSet for natural ordering, etc.), without inferring any specific implementation (e.g., ArrayList, HashSet, etc.). The flipside of this notion is that it's a mistake to use an overly specific class/interface - when your parameter type is ArrayList, you implicitly tell the user the *order* of his objects matter, and that it matters to your internal algorithm to be able to do get(i) as an O(1) operation. Bottom line, now that I'm done with CS 101: +1, but be careful not use interfaces that are too low. Most methods that now receive an ArrayList will still compile if you change the parameter type to Collection, but make sure that you don't implicitly assume some ordering, e.g. -Allon ----- Original Message -----