StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
6978482
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-08T06:30:32.393
FavoriteCount
0
LastActivityDate
2011-08-08T06:30:32.393
LastEditDate
LastEditorUserId
0
OwnerUserId
882968
ParentId
6970873
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
In reading: <ul> <li>You might not be used to that coding style, and might think that this executes the two functions: <pre><code>if(foo) bar(); baz(); </code></pre></li> <li>Since JS has automatic semicolon insertion, there are even murkier circumstances. I, for instance, am not comfortable with what ASI would do to this code, even if I can reason it out: <pre><code>if(foo) bar() baz() </code></pre> It is not impossible to figure out or even hard if you know what ASI does, but ASI is a nontrivial algorithm. Having to run it in your head is expensive in terms of time, so it's better if you simply avoid ambiguous (in this sense, not ambiguous as per the ECMA-262 spec) situations.</li> <li>It makes your lines longer than they need to be. This may be considered a non-issue depending on your coding conventions, if your condition is long, and your statement is as well, the resulting single-line statement will be more taxing on the eyes to read (it is well known that your eyes have difficulty reading very lone lines, hence paragraphing). You can, if you for some reason despite braces, still use something of the form: <pre><code>if(foo) bar(); </code></pre> And that is virtually identical to the code you had, but I see no reason, at that point, not to just put the braces there.</li> </ul> In writing: <ul> <li>When you need to add another statement, it is not the case that you'll simply write it. You will have to refactor the surrounding area in order to do this. Again, this is not hard at all, but it is something extra to think about, which is not related to neither your problem nor your solution of the problem, it is merely a syntactical quirk. I think you already get the point, but it would be this scenario. Initial code: <pre><code>if(foo) bar(); </code></pre> Changed code: <pre><code>if(foo) bar(); baz(); </code></pre> You can see the problem clearly, but it might not necessarily pop up in a routine code review. If your testcases don't cover this specific codepath, this might get pushed to production because of repeated coder oversights, which are made easier by not requiring blocks be delimited explicitly. The solution you'd could adopt, as you have, is to say something like <code>if(foo) bar() && baz()</code>, but that would fail if <code>bar()</code> is falsy, so you end up with ugly stuff like <code>if(foo) (bar(), baz());</code> which works, but is decidedly very ugly.</li> </ul> <hr> Personally, I use single-line <code>if</code> statements solely when the line is very short, and the algorithm itself is short as well. Something like <code>if(extra_loop) --i;</code> or <code>if(!valid) break;</code> When you start adding <code>else</code>s to these single-line ifs, the structure becomes more and more dangerous to manipulate. In short, you can use it, but use it knowing the pros and cons, just like any other tool.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POJSLint Braces around If-Block
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USFederico Lebrón
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POJSLint Braces around If-Block
 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.