Re: where's your Vector, victor
On 5/30/2014 10:32 AM, Knute Johnson wrote:
On 5/30/2014 01:11, bob smith wrote:
I read that the Vector class is obsolete.
Can someone tell me in a nutshell why this is so?
Thank you.
Mostly mythology. The Vector provides some additional functionality
over a synchronized List but it's probably not something you will need.
I'm "mostly" in agreement. For curiosity's sake, though, I ran
a few simple timing tests and found that Vector took about 35% more
time than ArrayList (for the mix of operations I tried).
"That's HU-U-U-GE!" somebody's shouting, but does it truly make a
difference? What else is the program doing, and how much time does it
spend on things other than List manipulation? Like, say, constructing
the things that go into the Lists, ruminating about which Lists they
belong in, converting them to and from XML, ...?
FWIW, the same tests also found that the List formed by applying
Collections.synchronizedList() to an ArrayList was about 5% slower
than Vector ...
If you don't need any synchronization then use an ArrayList, if you do
the Vector will work fine too.
I use Vector every time I can just to send the big giant heads into a
tizzy.
:)
Also, there are a few API's in the core Java suite that still deal
in Vectors, particularly in Swing: DefaultComboBoxModel, JList, JTree,
DefaultTableModel, ...
--
Eric Sosman
esosman@comcast-dot-net.invalid