StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18443275
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-08-26T11:42:39.253
FavoriteCount
0
LastActivityDate
2013-08-26T11:42:39.253
LastEditDate
LastEditorUserId
0
OwnerUserId
1056003
ParentId
18442839
PostTypeId
2
Score
1
ViewCount
0
LastEditorDisplayName
text
Body
<code>const</code> after a member function means that the function does not modify the state of the parent object: <pre><code>struct foo { int bar() const; // does not modify the instance of foo int & bar(); // might modify the instance of foo }; </code></pre> In your example your functions return <pre><code>int const * const </code></pre> The first <code>const</code> means, that the <code>int</code> you are pointing to must not be changed; you tell your user that he may read the value, but not modify it. This is also relevant for <code>const</code>-correctness: <pre><code>int const * foo() const; // can be used from const functions int * foo(); // cannot be used from const function </code></pre> The second <code>const</code> means that the pointer itself is <code>const</code>, meaning that: <pre><code>int * ptr = &a; *ptr = 42; // valid ptr = &b; // valid int const * ptr = &a; *ptr = 42; // INVALID ptr = &b; // valid int * ptr const = &a; *ptr = 42; // valid ptr = &b; // INVALID int const * ptr const = &a; *ptr = 42; // INVALID ptr = &b; // INVALID </code></pre> Making the pointer itself <code>const</code> as return value from a function is hardly ever useful. For references, a quick guide for C++03 is that you want to pass by reference if you want to modify the object, and want the modification to stick; you pass by value if you want to modify the object but do not want the modification to stick (a copy is made), or (exception!) if the value you are passing is a POD type; you pass by constant reference if you do not need to modify a non-POD type and thus save yourself the copy costs: <pre><code>void foo(int & a); // changes to a are applied to a itself, no copy made void foo(int a); // changes to a are applied to a copy of a, copy made void foo(std::string const & a); // no changes allowed, no copy made </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to access functionality of both GPU & SoundCard Chip directly from C++?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USnijansen
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
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.