StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
19142957
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-10-02T17:21:54.833
FavoriteCount
0
LastActivityDate
2013-10-02T17:21:54.833
LastEditDate
LastEditorUserId
0
OwnerUserId
1177073
ParentId
19142393
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
This doesn't directly answer the interviewer's question, but another possible way manipulating the inheritance of A and B is to do something like this: <pre><code>#include <iostream> #include <memory> #include <vector> using namespace std; //This concept was taken from a Going Native 2013 talk called "C++ Seasoning" given by Sean Parent // //Located here: (about 101 minutes into it) //http://channel9.msdn.com/Events/GoingNative/2013/Cpp-Seasoning //Polymorphism without inheritance. //Permits polymorphism without using pointers or references, //and allows them to be copied around easier (each instance is actually its own object) rather //than accidentally shallow-copying when you wanted deep-copies. // //Every time Object::Print() is called, it calls // Object::PrintableConcept::Print(), which virtually calls // Object::PrintableModel<TYPE>::Print(), which calls your // "derived" class that implements the Print() function, regardless // of what that class inherits (if anything). class Object //Class without inheritance or virtual. { public: template<typename Type> Object(Type instance) : self(std::make_shared<PrintableModel<Type>>(std::move(instance))) { } //Calls the "inherited" function. void Print() const { self->Print(); } private: struct PrintableConcept //The concept we want to polymorphably access. { virtual ~PrintableConcept() = default; virtual void Print() const = 0; }; //The class that concretely models the concept, //and does the actual inheritting. template<typename Type> struct PrintableModel : public PrintableConcept { PrintableModel(Type instance) : data(std::move(instance)) { } //Every time void Print() const override { this->data.Print(); } Type data; }; //This should be a unique_ptr, but you also need to make sure //you implement proper copy operators in this class and move support. std::shared_ptr<PrintableConcept> self; }; class Whatever { public: void Print() const { std::cout << "Whatever\n" << std::endl; } }; class SomethingElse { public: void Print() const { std::cout << "SomethingElse\n" << std::endl; } }; class WidgetThing { public: void Print() const { std::cout << "WidgetThing\n" << std::endl; } }; typedef std::vector<Object> Document; int main() { Document document; document.emplace_back(Whatever()); document.emplace_back(SomethingElse()); document.emplace_back(WidgetThing()); for(const auto &object : document) { object.Print(); } return 0; } </code></pre> <<< <a href="http://ideone.com/R5xEs4" rel="nofollow">Run the code</a> >>> None of the classes actually inherit from 'Object' (or from anything else), but can be used interchangeably with each other in, say, a vector, because they all implement a common interface (<code>PrintableConcept</code>) that Object accesses templatedly, but Object itself isn't a template and so doesn't become <code>Object<something></code> and <code>Object<something-else></code> which would've been separate types.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. PONot Inherit from Base Class C++
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJamin Grey
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. This table or related slice is empty.
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.