StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
443447
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2009-01-14T15:51:21.553
FavoriteCount
0
LastActivityDate
2009-01-14T15:51:21.553
LastEditDate
LastEditorUserId
0
OwnerUserId
8446
ParentId
443147
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
It depends. If you're talking about a static library, then you'll probably be OK -- the code will run in the same context as the main program, using the same C++ runtime library. This means that <code>new</code> and <code>delete</code> will use the same heap. If you're talking about a shared library (a DLL), then you probably won't be OK. The code running in the DLL might be using a different C++ runtime library, which means that the layout of the heap will be different. The DLL might be using a different heap altogether. Calling <code>delete</code> (in the main program) on a pointer allocated by the DLL (or vice versa) will lead to (at best) an immediate crash or (at worst) memory corruption that'll take a while to track down. You've got a couple of options. The first is to use the "factory method" pattern to create and delete these objects: <pre><code>Foo *CreateFoo(); void DeleteFoo(Foo *p); </code></pre> These should not be implemented in the header file. Alternatively, you can define a <code>Destroy</code> method on the object: <pre><code>class Foo { ~Foo(); public: virtual void Destroy(); }; </code></pre> ...again, don't implement this in the header file. You'd implement it thus: <pre><code>void Foo::Destroy() { delete this; // don't do anything that accesses this object past this point. } </code></pre> Note that the destructor for Foo is private, so that you have to call <code>Foo::Destroy</code>. Microsoft COM does something similar, where it defines a <code>Release</code> method that deletes the object when its reference count drops to zero.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ mix new/delete between libs?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USRoger Lipscombe
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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
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.