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: C++
Expertise: Intermediate
Sep 5, 2000

WEBINAR:

On-Demand

Application Security Testing: An Integral Part of DevOps


Container of Pointers

Many programmers believe that by storing pointers instead of objects in a container, they improve performance. However, they forget that the pointers still refer to existing objects that must be stored somewhere. Worse yet, these objects are often allocated dynamically. Dynamic allocation is an expensive operation. Remember also that you have to destroy these objects as well, which is another costly operation. Perhaps the most compelling argument against the use of pointers as container elements is that you can easily avoid the overhead associated with moving objects in memory by pre-allocating enough storage for the container in advance. This will ensure that no reallocation takes place, hence, no objects are moved around. You can pre-allocate storage by calling the reserve() member function:

 
std::vector < std::string > v;
v.reserve(1000);  // make room for at least 1000 strings

In most cases, an empirical test will show that the overall performance of object containers is superior to the performance of pointer containers. In other words, the use of pointers is a classic example of premature optimization.

Danny Kalev
 
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