I'm more and more convinced that the design decision to create the
classes
and interfaces (and how they're structured) is sound. So much so
that when
I find some time, I plan to write up a knowledge base article
discussing the
topic.
We have a knowledge base? ;-)
...to the application developer who doesn't want name conflicts, the
answer
is: don't use the "native" classes if you don't want to - use the JDK
collections, and wrap them in Pivot adapter classes where you have to.
I think this is the right approach. It doesn't force us to muddy our
API by applying contrived names to what are currently very aptly named
collection classes, and circumvents potential naming collisions for
the developers who would prefer to avoid them.
G
