StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
7150508
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2011-08-22T16:27:31.820
FavoriteCount
0
LastActivityDate
2011-08-22T16:27:31.820
LastEditDate
LastEditorUserId
0
OwnerUserId
36723
ParentId
7150475
PostTypeId
2
Score
4
ViewCount
0
LastEditorDisplayName
text
Body
While it is possible to cast to <code>void *</code> and back, the problem is knowing which type you're popping. After all, you give the example: <pre><code>Container<string> b = *reinterpret_cast<Container<string>*>(_collection.pop()); Container<int> a = *reinterpret_cast<Container<int>*>(_collection.pop()); </code></pre> However, if you were to accidentally do: <pre><code>Container<int> a = *reinterpret_cast<Container<int>*>(_collection.pop()); Container<string> b = *reinterpret_cast<Container<string>*>(_collection.pop()); </code></pre> Now you've got pointers to the wrong type, and will likely see crashes - or worse. If you want to do something like this, at least use <code>dynamic_cast</code> to check that you have the right types. With <code>dynamic_cast</code>, you can have C++ check, at runtime (using <a href="http://en.wikipedia.org/wiki/Run-time_type_information" rel="nofollow">RTTI</a>), that your cast is safe, as long as the types being casted (both before and after) have a common base type with at least one virtual method. So, first create a common base type with a virtual destructor: <pre><code>class ContainerBase { public: virtual ~ContainerBase() { } }; </code></pre> Make your containers derive from it: <pre><code>template <typename T> class Container : public ContainerBase { // ... } </code></pre> Now use a <code>std::stack<ContainerBase *></code>. When you retrieve items from the stack, use <code>dynamic_cast<Container<int> >(stack.pop())</code> or <code>dynamic_cast<Container<string> >(stack.pop())</code>; if you have the types wrong, these will check, and will return NULL. That said, heterogeneous containers are almost always the wrong thing to be using; at some level you need to know what's in the container so you can actually use it. What are you actually trying to accomplish by creating a container like this?
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POcontainer of unrelated T in c++
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USbdonlan
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POcontainer of unrelated T in c++
 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.