StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19615535
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-10-27T07:07:12.540
FavoriteCount
0
LastActivityDate
2013-10-27T07:07:12.540
LastEditDate
LastEditorUserId
0
OwnerUserId
34855
ParentId
19615355
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
<blockquote> I want to ask about passing pointers between functions or between objects or returning them .. I heard that passing or returning pointers in general (whether they point to an array or an object or whatever they are pointing at) isn't safe and the output isn't guaranteed. </blockquote> Where did you get that from? In general, it's not true and of course you can pass around pointers. The tricky thing is managing ownership of (heap-allocated) objects, since somewhere you have to release the memory again. In other words: When you allocate memory with <code>new</code>, you will have to free it again with <code>delete</code>. Example: <pre><code>A* function1(A* a) { return a; } B* function2(B* b) { return new B(b); } </code></pre> <code>function1</code> returns an existing pointer. Whoever owned the <code>A</code> object passed in will also own the returned one, as it is the same. This needs to be documented since this knowledge is essential for using <code>function1</code>! <code>function2</code> creates a new object of class <code>B</code> by coping its input argument. Whoever calls <code>function2</code> will own the returned object and will be responsible to <code>delete</code> it when it's done. Again, this needs to be documented! <blockquote> also, I read in a tutorial that everything in c++ is pass by value? isn't passing pointers is called pass by reference? </blockquote> Technically, passing pointers is pass-by-value since the pointer itself gets copied. But since a pointer is a "reference type", you essentially get pass-by-reference with that. Note that C++ also knows references (<code>int&</code>), which really is pass-by-reference.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPassing pointers between objects in c++
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFerdinand Beyer
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. COthanks Ferdinand, your answer really helped ^_^
 singulars
 PostPostId
 PO
 UserUserId
 USM.R.M

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.