StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POchar vs wchar_t vs char16_t vs char32_t (c++11)
primarykey
Id
19068748
data
AcceptedAnswerId
19069197
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-09-28T15:52:38.153
FavoriteCount
9
LastActivityDate
2014-10-30T10:56:52.070
LastEditDate
LastEditorUserId
0
OwnerUserId
904963
ParentId
0
PostTypeId
1
Score
38
ViewCount
20062
LastEditorDisplayName
text
Body
<p>From what I understand, a <code>char</code> is safe to house ASCII characters whereas <code>char16_t</code> and <code>char32_t</code> are safe to house characters from unicode, one for the 16-bit variety and another for the 32-bit variety (Should I have said "a" instead of "the"?). But I'm then left wondering what the purpose behind the <code>wchar_t</code> is. Should I ever use that type in new code, or is it simply there to support old code? What was the purpose of <code>wchar_t</code> in old code if, from what I understand, its size had no guarantee to be bigger than a <code>char</code>? Clarification would be nice!</p>
Tags
<c++><c++11>
Title
char vs wchar_t vs char16_t vs char32_t (c++11)
singulars
PostAcceptedAnswerId
1. PO
  singulars
  PostTypePostTypeId
  PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USuser904963
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. PO
  singulars
  PostTypePostTypeId
  PTAnswer
2. PO
  singulars
  PostTypePostTypeId
  PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
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.