StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
20577958
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-12-13T23:51:14.603
FavoriteCount
0
LastActivityDate
2016-03-06T16:02:33.970
LastEditDate
2016-03-06T16:02:33.970
LastEditorUserId
2072700
OwnerUserId
2072700
ParentId
20448882
PostTypeId
2
Score
16
ViewCount
0
LastEditorDisplayName
text
Body
The cluttered structure of C11 types resulting from the second step of the question can be simplified by removal/reduction of less important nodes and delegating some redundant/subsidiary information to be presented by other means. I propose the following five-step algorithm for that: <ol> <li>Removal of all extended integer types (strictly conforming implementation assumed);</li> <li>Reduction of the standard integer types (as they do not partition types any more);</li> <li>Grouping the structure: <ol> <li>A scalar types vs aggregate types pair of sub-trees (represented as a tree),</li> <li>A basic types vs derived types pair of sub-trees (represented by coloured regions),</li> <li>real types and derived declarator types (represented as stroked sub-regions of these),</li> <li>character types (represented with different text colour);</li> </ol></li> <li>Application of an off-standard production: object types = scalar types + aggregate types;</li> <li>Supplementing the object types of missing union types and atomic types.</li> </ol> The resulting C11 type system summary looks as follows: <a href="https://i.stack.imgur.com/f2dAp.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/f2dAp.png" alt="C11 type hierarchy"></a> The grey stroke/areas are introduced to increase readability of the tree. The type summary does not include the concept of "type declaration completeness" because it is a state, observed at a particular point within a translation unit. At run-time, all objects and functions are instances of a complete type. The <code>void</code> type is an exception but, as a no-type (or any-type in case of a pointer), it is intentionally excluded from the diagram. The <code>const</code>, <code>volatile</code>, <code>restrict</code> and <code>_Atomic</code> are type qualifiers which, contrary to type specifiers for the derived types, cannot be applied recursively. Any combination of these may prepend any type definition (as long as it makes sense). Thus, including them in the diagram would complicate it, while not introducing any suitable information. The apparent exception makes the <code>_Atomic (type)</code> construct, which is taken into account as being a type specifier for the atomic type – one of the derived types listed in the C11 standard.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POUnderstanding the C11 type hierarchy
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USKrzysztof Abramowicz
UserOwnerUserId
1. USKrzysztof Abramowicz
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POUnderstanding the C11 type hierarchy
 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.