StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
9661580
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-03-12T04:00:35.970
FavoriteCount
0
LastActivityDate
2012-03-12T04:00:35.970
LastEditDate
LastEditorUserId
0
OwnerUserId
514235
ParentId
9477581
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
I found one mechanism, where at least we are prompted to announce the overridden method explicitly. It's not the perfect way, but at least somewhat near. Suppose, we have few pure <code>virtual</code> methods in <code>class B</code> (base): <pre><code>class B { virtual void foo () = 0; virtual void bar (int) = 0; }; </code></pre> Among them, I want <code>foo()</code> to be overridden by the whole hierarchy, then abstract <code>foo()</code> 1 level up for simplicity: <pre><code>class Register_foo { template<typename T> // this matches the signature of 'foo' Register_foo (void (T::*)()) {} }; class Base : public virtual Register_foo { // <---- virtual inheritance virtual void bar (int) = 0; Base () : Register_foo(&Base::foo) {} // <--- explicitly pass the function name }; </code></pre> Every subsequent child class in the hierarchy would have to register its <code>foo</code> inside its every constructor explicitly. e.g.: <pre><code>struct D : B { D () : Register_foo(&D::foo) {} D (const D &other) : Register_foo(&D::foo) {} virtual void foo () {}; }; </code></pre> This registration mechanism has nothing to do with the business logic. But at least inside the constructor of any child class it would be mentioned that, which <code>foo</code> it's using. Though, the child <code>class</code> can choose to register using its own <code>foo</code> or its parent's <code>foo</code>, but at least that is announced explicitly. 
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POForce all classes to implement / override a 'pure virtual' method in multi-level inheritance hierarchy
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USiammilind
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POForce all classes to implement / override a 'pure virtual' method in multi-level inheritance hierarchy
 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
 VTAcceptedByOriginator
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.