dcsimg
Login | Register   
RSS Feed
Download our iPhone app
TODAY'S HEADLINES  |   ARTICLE ARCHIVE  |   FORUMS  |   TIP BANK
Browse DevX
Sign up for e-mail newsletters from DevX

By submitting your information, you agree that devx.com may send you DevX offers via email, phone and text message, as well as email offers about other products and services that DevX believes may be of interest to you. DevX will process your information in accordance with the Quinstreet Privacy Policy.


Tip of the Day
Language: Java
Expertise: Intermediate
Jun 16, 1999

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Vector vs. Array--the Best of Both Worlds

It's often pointed out that the Vector class is expensive to use because all of the methods are synchronized. Java 2 has the LinkedList class, which can serve the same purpose without the performance penalty. In the meantime, however, there's a simple approach you can take to one common use of Vectors that largely avoids the performance problem.

Often you use a Vector during the configuration stage of an application to create and hold objects of some sort because there's no way to tell ahead of time how many objects will be needed. At the end of configuration, however, the list won't change. The compromise is to use a Vector to build the list, and then turn the list into an array. For instance, suppose vec is the name of the Vector, and it holds objects of type MyObject:

 
  int nSize = vec.size();
  MyObject aobj = new MyObject[nSize];
  vec.copyInto(aobj);

The copyInto() method copies the Vector elements into the specified array. Thereafter, you can use the array as a much faster container for those objects, and you can discard the Vector.

Duane Morse
 
Comment and Contribute

 

 

 

 

 


(Maximum characters: 1200). You have 1200 characters left.

 

 

Sitemap
Thanks for your registration, follow us on our social networks to keep up-to-date