StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20672298
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-19T02:19:46.203
FavoriteCount
0
LastActivityDate
2013-12-19T02:19:46.203
LastEditDate
LastEditorUserId
0
OwnerUserId
2354107
ParentId
20672226
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
The <code>case</code> statements in a <code>switch()</code> have the same semantics as <code>goto</code>: When you dispatch to a label in a <code>switch</code>-<code>case</code>, you effectively <code>goto</code> the <code>case</code> label. The reason for this is that cases in a <code>switch</code>-<code>case</code> aren't self-contained. You can fall-through from one case to another. In fact, <code>switch</code>-<code>case</code> is so <code>goto</code>-like that you can even write a monstrosity such as <a href="http://en.wikipedia.org/wiki/Duff%27s_device" rel="nofollow">Duff's Device</a>. Study that until you're properly horrified. In C++, locally defined objects come into scope at their point of definition, and go out of scope at the closing curly brace of the enclosing scope. A <code>break</code> or <code>continue</code> statement that exits that scope is guaranteed to cleanly handle objects going out of scope. For your <code>switch</code> statement, the enclosing scope is defined by the curly-braces after <code>switch()</code>. Now, in C++, it's illegal to use <code>goto</code> or something like it skip an object initialization. In your example, the <code>case</code> and <code>default</code> labels run afoul of that rule. Your fix avoids the issue by replacing object initialization with object assignment. That's one way to fix it. Another is to add an additional level of scope: <pre><code> case WM_LBUTTONDOWN: { HBRUSH hBrush = CreateSolidBrush(RGB(0, 0, 0)); break; } </code></pre> This works because the curly braces provide an extra level of scope clearly defining when <code>hBrush</code>'s lifetime ends. In terms of technical detail: The statement that triggered the error relies on a copy constructor. The statement that did not relies on the copy assignment operator instead.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POWhy I can't initialize a variable in switch case block
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJoe Z
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
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.