StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14366136
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-01-16T19:23:39.920
FavoriteCount
0
LastActivityDate
2013-01-16T21:24:03.717
LastEditDate
2013-01-16T21:24:03.717
LastEditorUserId
1413374
OwnerUserId
1413374
ParentId
14366029
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Here <pre><code>i->parent = pBase(this); </code></pre> you create a smart pointer from a plain old pointer to an object which you didn't get directly from new. Never do this. As @Roddy explained, you get separate smart pointer objects, with separate reference counters. Two reference counters for one pointee won't work. In your case, it's probably ok to make parent a normal pointer, as @Roddy proposed. This way, you don't get in trouble with cyclic references. Just be sure that you never access the parent pointer after you deleted the parent. No problem if you delete all the children together with the parent (which happens automatically, unless you store more smart pointers to them, somewhere else) If you want to initialize a smart pointer, you've got two choices, basically: Use smart pointers in every interface. Unfortunately that doesn't work for "this" because that's an implicit parameter. You would need to pass the smart pointer, which you already created, to the method manually, in an extra parameter. Like this: <pre><code>tree->add(tree, child); </code></pre> Which is kind of ugly, so you may want to consider making "add" a static method, so you won't need to pass the parent twice. The other choice: Use another kind of smart pointer, like boost::intrusive_ptr, where you can store the reference count in the pointee. This way, you are able to find the reference count, even if you've got only a dumb pointer like "this". Edit: The answer by @jpalecek, below, is better. Use that one. Sebastian.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ shared_ptr<Base> pointer acces violation
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USSebastian
UserOwnerUserId
1. USSebastian
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. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
2. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COAh thank you very much!
 singulars
 PostPostId
 PO
 UserUserId
 USTim

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.