StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4014707
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-10-25T12:53:47.830
FavoriteCount
0
LastActivityDate
2010-10-25T12:53:47.830
LastEditDate
LastEditorUserId
0
OwnerUserId
321013
ParentId
3161991
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You can only use the stack as storage space when you know at compile time how big the storage you are going to need is. It follows that you can use the stack for <ul> <li>Single objects (like you do declare a local <code>int</code> or <code>double</code> or <code>MyClass temp1;</code> variable</li> <li>statically-sized arrays (like you do when you declare <code>char local_buf[100];</code> or <code>MyDecimal numbers[10];</code></li> </ul> You have to use the heap ("free store") when you only know how much space you need at runtime and you should probably use the heap for large statically known buffers (like don't do <code>char large_buf[32*1024*1024];</code> ) Normally however, you very seldomly should touch the heap directly, but normally use objects that manage some heap memory for you (and the object possibly lives on the stack or as member of another object - where you then don't care where the other object lives) To give some example code: <pre><code>{ char locBuf[100]; // 100 character buffer on the stack std::string s; // the object s will live on the stack myReadLine(locBuf, 100); // copies 100 input bytes to the buffer on the stack s = myReadLine2(); // at this point, s, the object, is living on the stack - however // inside s there is a pointer to some heap allocated storage where it // saved the return data from myReadLine2(). } // <- here locBuf and s go out-of-scope, which automatically "frees" all // memory they used. In the case of locBuf it is a noop and in the case of // s the dtor of s will be called which in turn will release (via delete) // the internal buffer s used. </code></pre> So to give a short answer to your question when: Don't allocate anything on the heap (via <code>new</code>) unless this is done via an appropriate wrapper object. (std::string, std::vector, etc.)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhen should I allocate on the heap? (C++)
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USMartin Ba
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.