StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
18288403
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2013-08-17T11:41:32.313
FavoriteCount
0
LastActivityDate
2013-08-17T11:41:32.313
LastEditDate
LastEditorUserId
0
OwnerUserId
142182
ParentId
18140630
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
Performance efficiency - more efficient but only by a few instructions, storing and loading the variable from the execution stack. Bear in mind that the Jitter may optimise your code at run-time, removing any unnecessary instructions. Memory efficiency - more efficient as there is no local var defined on the execution stack. Code clarity - having the definition of a variable closer to where it's used makes the code more usable. In my opinion having the one method returning into another is even cleaner however does have the downside that it's harder to inspect the value being returned (in VS 2013 this will be possible however). IL with the temp variable: <pre><code> // Code size 13 (0xd) .maxstack 1 .locals init ([0] int32 myVar) IL_0000: call int32 StackOverflowScratchPad.Program::FunctionThatReturnsAnInteger() IL_0005: stloc.0 IL_0006: ldloc.0 IL_0007: call void [mscorlib]System.Console::WriteLine(int32) IL_000c: ret </code></pre> and without: <pre><code> // Code size 11 (0xb) .maxstack 8 IL_0000: call int32 StackOverflowScratchPad.Program::FunctionThatReturnsAnInteger() IL_0005: call void [mscorlib]System.Console::WriteLine(int32) IL_000a: ret </code></pre> Bonus - IL when assigning an value to temp var at the declaration: <pre><code> // Code size 15 (0xf) .maxstack 1 .locals init ([0] int32 myVar) IL_0000: ldc.i4.5 IL_0001: stloc.0 IL_0002: call int32 StackOverflowScratchPad.Program::FunctionThatReturnsAnInteger() IL_0007: stloc.0 IL_0008: ldloc.0 IL_0009: call void [mscorlib]System.Console::WriteLine(int32) IL_000e: ret </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PODoes declaring a variable already occupy memory
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USSlugart
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. PODoes declaring a variable already occupy memory
 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
 VTAcceptedByOriginator
CommentsPostId
1. COThank you very much for your wonderful answer! +1 for you :)
 singulars
 PostPostId
 PO
 UserUserId
 USKiX Ortillan

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.