StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4479652
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-12-18T19:15:09.897
FavoriteCount
0
LastActivityDate
2014-02-06T10:29:10.327
LastEditDate
2017-05-23T11:54:48.027
LastEditorUserId
-1
OwnerUserId
415784
ParentId
4479597
PostTypeId
2
Score
97
ViewCount
0
LastEditorDisplayName
text
Body
Another question can be asked (or simply another way to look at the original question): <h2>Does making a struct <code>const</code> make all its members <code>const</code>?</h2> If I have: <pre><code>struct whatever { int data; }; const whatever test; </code></pre> Will test.data be <code>const</code> too? My answer is : Yes. If you declare an object of type <code>whatever</code> with <code>const</code> then all its members will be <code>const</code> too Similarly, if you declare an object of type <code>whatever</code> with <code>volatile</code> then all its members will be <code>volatile</code> too, just like if you declare the object with <code>const</code>, all it's member will be <code>const</code> too. <code>const</code> and <code>volatile</code> are two faces of the same coin; they're so that the Standard often refers to them as <code>cv-qualifiers</code>. <hr> Quoting from the Standard ($7.1.5.1/8) <blockquote> [Note: volatile is a hint to the implementation to avoid aggressive optimization involving the object because the value of the object might be changed by means undetectable by an implementation. See 1.9 for detailed semantics. In general, the semantics of volatile are intended to be the same in C + + as they are in C. ] </blockquote> That means, if your object is an instance of a struct, then the compiler cannot avoid aggressive optimization involving the object, unless it avoids aggressive optimization of each of it's members. (Otherwise, how else it can avoid optimization involving the object?) <hr> Related topic: <a href="https://stackoverflow.com/questions/4437527/why-do-we-use-volatile-keyword-in-c/4437555#4437555">Why do we use volatile keyword in C++?</a>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODoes making a struct volatile make all its members volatile?
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USNawaz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODoes making a struct volatile make all its members volatile?
 singulars
 PostTypePostTypeId
 PTQuestion
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
 VTAcceptedByOriginator
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.