Greg Brown wrote: > Yes, it might be a pain to combine a Pivot ArrayList and a JDK > ArrayList in the same source file, but realistically, that's not > likely to happen very often. If you are writing a Pivot app, you are > most likely going to be using Pivot collections (at least, in your > Pivot code). You may have some server-side code that uses JDK > collections, but, in general, that shouldn't conflict with what you > are doing in the UI. On the other hand, if you are using Pivot's > QueryServlet class, you may find that you want to use Pivot's > collections on the server as well. It's not really a case of combining them in the same file. It's that in a large Pivot project, by necessity, (a) you are going to have lots of code using both pivot's ArrayList and java's ArrayList (b) you are going to be staring at code that you did not write
If you open some random file and starting looking at code, it's very annoying to suddenly discover that what you thought was a Pivot ArrayList is, in fact, a Java ArrayList, or vice versa. While I don't generally like assigning prefixes to classnames, I have found it to be a very useful means of reducing the cognitive load required when scanning through our codebase. -- Noel.
