Re: [Flightgear-devel] vector.push_back() and the d'tor

2004-04-07 Thread Gerhard Wesp
On Tue, Apr 06, 2004 at 09:03:51PM -0500, Jon Berndt wrote: I'm not positive, but it seems (roughly) like a vector push_back() operation causes the d'tor to be called after the first element is stored. To me, this Yes, if capacity() changes on a resizing operation (like push_back()), the

Re: [Flightgear-devel] vector.push_back() and the d'tor

2004-04-07 Thread David Megginson
Jon Berndt wrote: I'm not positive, but it seems (roughly) like a vector push_back() operation causes the d'tor to be called after the first element is stored. To me, this seems to say that the push_back() operation copies the existing stored element[s] to a new location (resizing the container)

[Flightgear-devel] vector.push_back() and the d'tor

2004-04-06 Thread Jon Berndt
I'm not positive, but it seems (roughly) like a vector push_back() operation causes the d'tor to be called after the first element is stored. To me, this seems to say that the push_back() operation copies the existing stored element[s] to a new location (resizing the container) and destroys the

RE: [Flightgear-devel] vector.push_back() and the d'tor

2004-04-06 Thread Jon Berndt
I'm not positive, but it seems (roughly) like a vector push_back() operation causes the d'tor to be called after the first element is stored. To me, this seems to say that the push_back() operation copies the existing stored element[s] to a new location (resizing the container) and destroys