StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
11796966
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-08-03T13:43:30.827
FavoriteCount
0
LastActivityDate
2012-08-03T13:43:30.827
LastEditDate
LastEditorUserId
0
OwnerUserId
1527
ParentId
11796121
PostTypeId
2
Score
5
ViewCount
0
LastEditorDisplayName
text
Body
Your BaseVisitor does nothing for you, other than allowing arbitrary visitees to delete the visitor. Instead, you want to have a base class for the visitor which provides all of the different <code>accept</code> functions that could be called on it, and for the <code>Visitable</code> to accept this visitor. To do this, you could use a <a href="http://books.google.co.uk/books?id=aJ1av7UFBPwC&lpg=PA52&vq=type%20list&pg=PA51#v=onepage&q&f=false" rel="noreferrer">type list</a> to define the types the visitor can accept, have a base visitee class which takes the type list, and add the type list as a parameter to your visitee implementation. sketch of example: <pre><code>// assuming a typelist has typedefs first and second and a // type 'empty' representing end of type list template<typename Types> class Visitor : public Visitor<Types::second> { public: // visitor has a visit function for each type in Types virtual void visit(typename Types::first& visitable) = 0; }; template<> class Visitor<empty> { }; template<typename Types> class Visitable{ public: // base accepts a visitor which can visit any type in Types virtual void accept(Visitor<Types>& visitor) = 0; }; template<typename Derived, typename Types> class VisitableImpl : public Visitable<Types> { public: // impl calls specific visit function virtual void accept(Visitor<Types>& visitor) override { visitor.visit(static_cast<Derived&>(*this)); } }; </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POImplementing the visitor pattern using C++ Templates
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USPete Kirkham
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
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.