StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
5471923
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-03-29T11:41:14.180
FavoriteCount
0
LastActivityDate
2011-03-29T11:56:25.393
LastEditDate
2011-03-29T11:56:25.393
LastEditorUserId
158049
OwnerUserId
158049
ParentId
5471807
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
The question is quite vague... but either way, I guess that you are wondering if pointers stored in a <code>vector</code> would automatically be deleted when <code>clear()</code> is called. This is not the case. Whatever you store in a <code>vector</code> will have its destructor called when <code>clear()</code> occurs. And the destructor of a primitive type (such as a pointer) does.. nothing. From my SGI implementation: <pre><code>/** * Erases all the elements. Note that this function only erases the * elements, and that if the elements themselves are pointers, the * pointed-to memory is not touched in any way. Managing the pointer is * the user's responsibilty. */ void clear() { erase(begin(), end()); } </code></pre> To properly delete items pointers in any STL container, the easiest way is to create a functor and apply it on every item: <pre><code>#include <iostream> #include <cstdlib> #include <vector> #include <functional> #include <algorithm> template <typename ValueT> struct func_delete : public std::unary_function<ValueT,void> { void operator()( ValueT& item ) { delete item; } }; struct Foo { ~Foo() { std::cout << "Foo::~Foo()" << std::endl; } }; template <typename ContainerT> void delete_container( ContainerT& container ) { std::for_each( container.begin(), container.end(), func_delete<typename ContainerT::value_type>() ); } int main( int argc, char** argv ) { std::vector<Foo*> foos; foos.push_back( new Foo ); foos.push_back( new Foo ); foos.push_back( new Foo ); // Either of these two lines will work //std::for_each( foos.begin(), foos.end(), func_delete<Foo*>() ); //delete_container( foos ); foos.clear(); return EXIT_SUCCESS; } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POvector::clear :Memory Issue
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USNewbiZ
UserOwnerUserId
1. USNewbiZ
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.