std::vector::resize ,

[vsgdp]

On Page 67 of Effective STL, Meyers writes about resize: "If n is smaller
than the current size, elements at the end of the container will be
destroyed."

What does "destroyed" mean? It seems to me that if n is smaller than the
current size, simple adjust the internal size counter to n and be done.

[Bob Hairgrove]

On Mon, 17 Oct 2005 16:21:59 -0700, "vsgdp" <sp**@void.com> wrote:

On Page 67 of Effective STL, Meyers writes about resize: "If n is smaller
than the current size, elements at the end of the container will be
destroyed."

What does "destroyed" mean? It seems to me that if n is smaller than the
current size, simple adjust the internal size counter to n and be done.

Destroyed means that the destructor for each element is called ... a
vector can have elements of class type as well as POD-type.

--
Bob Hairgrove
No**********@Home.com

[Kai-Uwe Bux]

vsgdp wrote:

On Page 67 of Effective STL, Meyers writes about resize: "If n is smaller
than the current size, elements at the end of the container will be
destroyed."
It means that the destructors for these objects are called.

What does "destroyed" mean? It seems to me that if n is smaller than the
current size, simple adjust the internal size counter to n and be done.

That works for POD types and types with trivial destructor. However, the
compiler is not required to optimize the destructor calls away.
Best

Kai-Uwe Bux

[vsgdp]

"Kai-Uwe Bux" <jk********@gmx.net> wrote in message
news:dj**********@murdoch.acc.Virginia.EDU...

vsgdp wrote:

On Page 67 of Effective STL, Meyers writes about resize: "If n is smaller
than the current size, elements at the end of the container will be
destroyed."
It means that the destructors for these objects are called.

What does "destroyed" mean? It seems to me that if n is smaller than the
current size, simple adjust the internal size counter to n and be done.

That works for POD types and types with trivial destructor. However, the
compiler is not required to optimize the destructor calls away.

Thanks. What does POD mean? I still do not understand. If you had a
vector of some class type C with vector size n, and resize to a new size m <
n, why must the destructors be called? You can just leave the objects
sitting there--the memory is still there. Then is you call push_back later
on, you are essentially doing an assignment to the next element, thereby
overwriting it. C's overloaded operator = or copy constructor should take
care of doing a correct assignment.
Best

Kai-Uwe Bux

[red floyd]

vsgdp wrote:

Thanks. What does POD mean?
POD = Plain Old Data
I still do not understand. If you had a
vector of some class type C with vector size n, and resize to a new size m <
n, why must the destructors be called?

Because that's the way a container is defined in the Standard. If an
object is removed from a container, its destructor is called. And
resizing a vector to m, where m < n, is conceptually equivalent to
calling v.erase(v.begin() + m, v.end), or alternatively, calling
pop_back() n-m times.

[Kai-Uwe Bux]

vsgdp wrote:

"Kai-Uwe Bux" <jk********@gmx.net> wrote in message
news:dj**********@murdoch.acc.Virginia.EDU...

vsgdp wrote:

On Page 67 of Effective STL, Meyers writes about resize: "If n is
smaller than the current size, elements at the end of the container will
be destroyed."
It means that the destructors for these objects are called.

What does "destroyed" mean? It seems to me that if n is smaller than
the current size, simple adjust the internal size counter to n and be
done.

That works for POD types and types with trivial destructor. However, the
compiler is not required to optimize the destructor calls away.

Thanks. What does POD mean?

POD: plain old data

I still do not understand. If you had a vector of some class type C with vector size n, and resize to a new size m < n, why must the destructors be called? You can just leave the objects sitting there--the memory is still
there. Then is you call push_back later on, you are essentially doing an
assignment to the next element, thereby overwriting it. C's overloaded
operator = or copy constructor should take care of doing a correct
assignment.

If you want that, simply do not resize but overwrite the elements in the
vector. In C++ it is very important to *know* the lifetime of an object.
That is the reason that the standard says something. Whether you like what
the standard says or not is, of course, a different matter.
Best

Kai-Uwe Bux

[vsgdp]

I still do not understand. If you had a vector of some class type C with vector size n, and resize to a new size m < n, why must the destructors be

called? You can just leave the objects sitting there--the memory is
still
there. Then is you call push_back later on, you are essentially doing an
assignment to the next element, thereby overwriting it. C's overloaded
operator = or copy constructor should take care of doing a correct
assignment.

If you want that, simply do not resize but overwrite the elements in the
vector. In C++ it is very important to *know* the lifetime of an object.
That is the reason that the standard says something. Whether you like what
the standard says or not is, of course, a different matter.

I see. Okay, final question: is anything different for built in types? Say
if my std::vector contains ints? Do built in types have destructors?

Best

Kai-Uwe Bux

[Mike Wahler]

"vsgdp" <sp**@void.com> wrote in message
news:hRX4f.2875$i%.2572@fed1read07...

I see. Okay, final question: is anything different for built in types?
Say if my std::vector contains ints? Do built in types have destructors?

No.

-Mike

[Greg Comeau]

In article <71X4f.2865$i%.2742@fed1read07>, vsgdp <sp**@void.com> wrote:

What does POD mean?

Check out http://www.comeaucomputing.com/techtalk/#pod
--
Greg Comeau / Celebrating 20 years of Comeauity!
Comeau C/C++ ONLINE ==> http://www.comeaucomputing.com/tryitout
World Class Compilers: Breathtaking C++, Amazing C99, Fabulous C90.
Comeau C/C++ with Dinkumware's Libraries... Have you tried it?

[Ron Natalie]

Mike Wahler wrote:

"vsgdp" <sp**@void.com> wrote in message
news:hRX4f.2875$i%.2572@fed1read07...

I see. Okay, final question: is anything different for built in types?
Say if my std::vector contains ints? Do built in types have destructors?

No.

No they don't but I bet the vector implementation still calls the pseudo
destructor for them (of course the compiler most certainly optimizes
that away.

[Jim Langston]

"vsgdp" <sp**@void.com> wrote in message
news:71X4f.2865$i%.2742@fed1read07...

"Kai-Uwe Bux" <jk********@gmx.net> wrote in message
news:dj**********@murdoch.acc.Virginia.EDU...

vsgdp wrote:

On Page 67 of Effective STL, Meyers writes about resize: "If n is
smaller
than the current size, elements at the end of the container will be
destroyed."

It means that the destructors for these objects are called.

What does "destroyed" mean? It seems to me that if n is smaller than
the
current size, simple adjust the internal size counter to n and be done.

That works for POD types and types with trivial destructor. However, the
compiler is not required to optimize the destructor calls away.

Thanks. What does POD mean? I still do not understand. If you had a
vector of some class type C with vector size n, and resize to a new size m
< n, why must the destructors be called? You can just leave the objects
sitting there--the memory is still there. Then is you call push_back
later on, you are essentially doing an assignment to the next element,
thereby overwriting it. C's overloaded operator = or copy constructor
should take care of doing a correct assignment.

Consider a class that handles it's own memory:

class MyClass
{
public:
MyClass() { MyData = new char[10000]; }
~MyClass() { delete MyData; }
// copy/assigment not show for brevity
// but should be here for the "rule of 3"
private:
char* Mydata;
};

Push that onto a vector... now, if the container gets resized and the
destructor is my called there is a memory leak, in this case at least 10,000
bytes of data. Do that a few times and you leak a lot of memory.

Class destructors must *always* be called if the constructor is called,
otherwise there are memory leaks.