StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
4311095
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2010-11-30T06:23:32.833
FavoriteCount
0
LastActivityDate
2010-11-30T06:23:32.833
LastEditDate
LastEditorUserId
0
OwnerUserId
134633
ParentId
4310954
PostTypeId
2
Score
3
ViewCount
0
LastEditorDisplayName
text
Body
Conceptually, this is OK - but you have to do some additional work to ensure it will work reliably. A potential problem is that you cannot just access any arbitrary address as a <code>float</code>. There may be specific alignment requirements - the address returned by <code>malloc()</code> is required to be correctly aligned for access as any type, but once you add 14 to that address, all bets are off (except for <code>char</code>). To ensure the correct alignment, you must ensure that the address you add to <code>buffer</code> is a multiple of <code>sizeof(float)</code>. You can do that by adding padding using the following formula: <pre><code>#define PAD_OFFSET(offset, type) ((offset) + sizeof(type) - 1) & ~(sizeof(type) - 1)) float *float_buffer = (float *)(buffer + PAD_OFFSET(14, float)); </code></pre> Note that this will create a gap - padding - between your chars and your floats. Alternatively, you can define a <code>struct</code>, and the compiler will figure the padding out for you. This uses a C99 feature called a flexible array member: <pre><code>struct foo { char abc[14]; float xyz[]; }; struct foo *buffer = malloc(2062); memcpy(&buffer->abc, header, 14); some_function(&buffer->xyz); transmit(buffer); /* Presuming transmit() expects a void * parameter. */ </code></pre> If you wish to do it without padding, you cannot directly access the memory in <code>buffer</code> as floats - you will have to create a temporary array and copy it in: <pre><code>float temp[500]; /* Or whatever size */ some_function(&temp); memcpy(buffer + 14, temp, sizeof temp); </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POtreating allocated memory as a different type
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. UScaf
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. 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. COThanks yes it was alignment issue.
 singulars
 PostPostId
 PO
 UserUserId
 USeat_a_lemon

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.