StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
17327770
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-06-26T18:28:56.573
FavoriteCount
0
LastActivityDate
2013-06-26T18:28:56.573
LastEditDate
LastEditorUserId
0
OwnerUserId
300797
ParentId
16927304
PostTypeId
2
Score
-1
ViewCount
0
LastEditorDisplayName
text
Body
I strongly suggest you update your knowledge of pointers in C++. There is almost no reason to use raw pointers these days. To answer the question directly, the <code>Game.GetScreen()</code> function would want to 'const' differently depending on how exactly you wish for it behave. If you return a <code>const Screen*</code> you are returning a pointer to a Screen object that is constant (cannot be modified). You would normally wish to make such a function const allowing it to be called on a Game object that is const it self. If somebody has a non-const Game object, you can allow them to get the Screen object that they can then modify by simply returning a <code>Screen*</code>. That said, I return to my opening point, you shouldn't use raw pointers. Initially, you should just have the Screen object stored by value, and return references, giving you a class along the lines of: <pre><code>Class Game{ Screen screen; public: const Screen& GetScreen() const{ return screen; } Screen& GetScreen(){ return screen; } }; </code></pre> This may look like you are copying the Screen object to return it, but the return types ensure you are returning a reference to the same screen object, rather than a copy. If you really do need dynamic creation of the Screen object (ie, you cannot create it either before or as you create the Game object) then you should use a <code>std::unique_ptr<Screen></code>. This can be used very much like a raw pointer, but will take care of a lot of the functionality for you. However, you wish to share access to this Screen pointer, so you probably want to use <code>std::shared_ptr<Screen></code> and return <code>std::weak_ptr<Screen></code> from the the get function. The weak_ptr can be used to allow others access, but your initial Game object still owns the Screen object. Long story short, store the Screen object by value, and return references to it.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ Only Allow a member variable to be set once
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USthecoshman
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.