StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3274526
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
7
CommunityOwnedDate
CreationDate
2010-07-18T06:07:19.630
FavoriteCount
0
LastActivityDate
2010-07-18T12:36:04.237
LastEditDate
2010-07-18T12:36:04.237
LastEditorUserId
14860
OwnerUserId
14860
ParentId
3274472
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
There are a few approaches you can take, one of which involves storing a <code>void*</code> in your ADT. I've always found this to be a bit of a pain in a linked list since you have to manage it's allocation separately to the list itself. In other words, to allocate a node, you need to alocate both the node and its payload separately (and remember to clean them both up on deletion as well). One approach I've used in the past is to have a 'variable sized' structure like: <pre><code>typedef struct _tNode { struct _tNode *prev; struct _tNode *next; char payload[1]; } tNode; </code></pre> Now that doesn't look variable sized but let's allocate a structure thus: <pre><code>typedef struct { char Name[30]; char Addr[50]; char Phone[20]; } tPerson; tNode *node = malloc (sizeof (tNode) - 1 + sizeof (tPerson)); </code></pre> Now you have a node that, for all intents and purposes, looks like this: <pre><code>typedef struct _tNode { struct _tNode *prev; struct _tNode *next; char Name[30]; char Addr[50]; char Phone[20]; } tNode; </code></pre> or, in graphical form (where <code>[n]</code> means <code>n</code> bytes): <pre><code>+------------+ | prev[4] | +------------+ | next[4] | +------------+ +-----------+ | payload[1] | | Name[30] | <- overlap +------------+ +-----------+ | Addr[50] | +-----------+ | Phone[20] | +-----------+ </code></pre> That is, assuming you know how to address the payload correctly. This can be done as follows: <pre><code>node->prev = NULL; node->next = NULL; tPerson *person = &(node->payload); // cast for easy changes to payload. strcpy (person->Name, "Richard Cranium"); strcpy (person->Addr, "10 Smith St"); strcpy (person->Phone, "555-5555"); </code></pre> That cast line simply casts the address of the <code>payload</code> character (in the <code>tNode</code> type) to be an address of the actual <code>tPerson</code> payload type. Using this method, you can carry any payload type you want in a node, even different payload types in each node, if you make the structure more like: <pre><code>typedef struct _tNode { struct _tNode *prev; struct _tNode *next; int payloadType; // Allows different payload type at each node. char payload[1]; } tNode; </code></pre> and use <code>payloadType</code> to store an indicator as to what the payload actually is. This has the advantage over a union in that it doesn't waste space, as can be seen with the following: <pre><code>union { int fourBytes; char oneHundredBytes[100]; } u; </code></pre> where 96 bytes are wasted every time you store an integer type in the list (for a 4-byte integer). The payload type in the <code>tNode</code> allows you to easily detect what type of payload this node is carrying, so your code can decide how to process it. You can use something along the lines of: <pre><code>#define PAYLOAD_UNKNOWN 0 #define PAYLOAD_MANAGER 1 #define PAYLOAD_EMPLOYEE 2 #define PAYLOAD_CONTRACTOR 3 </code></pre> or (probably better): <pre><code>typedef enum { PAYLOAD_UNKNOWN, PAYLOAD_MANAGER, PAYLOAD_EMPLOYEE, PAYLOAD_CONTRACTOR } tPayLoad; </code></pre> The only thing you need to watch out for is to ensure that the alignment of the payload is correct. Since both my payload placeholder and the payload are all <code>char</code> types, that's not an issue. However, if your payload consists of types with more stringent alignment requirements (such as something more strict than the pointers, you may need to adjust for it). While I've never seen an environment with alignments more strict than pointers, it is possible according to the ISO C standard. You can usually get the required alignment simply by using a data type for the payload placeholder which has the strictest alignment requirement such as: <pre><code>long payload; </code></pre> <hr> In retrospect, it occurs to me that you probably don't need an array as the payload placeholder. It's simple enough to just have something you can take the address of. I suspect that particular idiom of mine hearkens back to the days where I just stored an array of characters (rather than a structure) and referenced them directly. In that case, you could use <code>payload[]</code> on its own without casting to another type.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC double linked list with abstract data type
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpaxdiablo
UserOwnerUserId
1. USpaxdiablo
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POC double linked list with abstract data type
 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

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.