StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
13167586
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-10-31T21:18:32.007
FavoriteCount
0
LastActivityDate
2012-10-31T21:50:19.073
LastEditDate
2012-10-31T21:50:19.073
LastEditorUserId
1322972
OwnerUserId
1322972
ParentId
13167437
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Fundamentally the calling side has no distinct difference. But the decl side definitely does. As you have pointed out, references must be initialized to reference something. This makes them "safer", but even then there is no guarantee of "safety". The function pointer need NOT point to a function at all. It could be NULL, or even uninitialized (pointing to garbage). Not that it matters, because you can always change it later (something you can NOT do with references). <pre><code>void (*s)(); // uninitialized </code></pre> or <pre><code>void (*s)() = NULL; // set to null </code></pre> and later <pre><code>void foo() { } s = foo; </code></pre> You can do none of those with a reference. The reference must be initialized to something and preferabley something valid: <pre><code>void (&f)() = foo; // ok. also references foo(). void (&f)() = *s; // also ok, but wait, is s valid?? does it have to be?? </code></pre> However, even here a function reference is not guaranteed to be safe, just safer. You can certainly do this: <pre><code>void (*s)(); void (&f)() = *s; </code></pre> You may get a compiler warning out of this (I do, "s used before being initialized") but in the end <code>f</code> still is now a reference to a "function" that isn't a function at all; just the random stack garbage in the <code>s</code> pointer. Worse, since references cannot be reassigned. this thing will always point at garbage. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POFunction-pointer syntax ambiguity
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USWhozCraig
UserOwnerUserId
1. USWhozCraig
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POFunction-pointer syntax ambiguity
 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
 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.