Login | Register   
RSS Feed
Download our iPhone app
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
Home » Tip Bank » C++
Language: C++
Expertise: Intermediate
Dec 16, 1998



Application Security Testing: An Integral Part of DevOps

What Happens When a Container Re-Allocates Itself?

When a container has exhausted its free storage and additional elements have to be inserted to it, the container re-allocates itself. First, a new memory buffer large enough to store the container is allocated. Existing elements are then copied to the new memory location. The destructors of the elements in their previous location are successively invoked. Finally, the original memory buffer is released. Clearly, frequent re-allocations can impose a significant performance overhead.
Danny Kalev
Comment and Contribute






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



We have made updates to our Privacy Policy to reflect the implementation of the General Data Protection Regulation.
Thanks for your registration, follow us on our social networks to keep up-to-date