StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
872744
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2009-05-16T16:22:39.067
FavoriteCount
0
LastActivityDate
2009-05-16T16:22:39.067
LastEditDate
LastEditorUserId
0
OwnerUserId
105634
ParentId
872675
PostTypeId
2
Score
12
ViewCount
0
LastEditorDisplayName
text
Body
This looks like a nice example of policy-based smart pointer implementation: <a href="http://axter.com/smartptr/classsmart__ptr.htm" rel="noreferrer">link</a>. <a href="http://en.wikipedia.org/wiki/Andrei_Alexandrescu" rel="noreferrer">Andrei Alexandrescu</a> describes policy-based smart pointer implementation in one of his books. As to your questions now. I have some experience in this stuff but not enough to take my words for granted: Ad 1 & 4. I guess policy-based design is more about templates than inheritance. You write a template class and template arguments are policy classes, like that: <pre><code>template<class FooPolicy, class BarPolicy> class Baz { // implementation goes here }; </code></pre> Then you use methods from policy classes in your class: <pre><code>void Baz::someMethod(int someArg) { FooPolicy::methodInit(); // some stuff BarPolicy::methodDone(); } </code></pre> I use static methods in this example because often policy doesn't require any state. If it does, you incorporate policy's state by composition, not by inheritance: <pre><code>template<class FooPolicy, class BarPolicy> class Baz { private: FooPolicy::State fooState; // might require 'typename' keyword, I didn't // actually tried this in any compiler // rest of the Baz class }; </code></pre> Ad 2. You can write a template specialization - for a particular combination of main class and it's policies you can write a special version of any method or constructor, AFAIK: <pre><code>template <> Baz<SomeConcreteFooPolicy, SomeConcreteBazPolicy>::Baz(someArgument) : fooState(someArgument) { // stuff here } </code></pre> Hope it helps you a bit, Mike
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPolicy based design and best practices - C++
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. This table or related slice is empty.
UserOwnerUserId
1. USJasiu
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
3. VO
 singulars
 PostPostId
 PO
 UserUserId
 This table or related slice is empty.
 VoteTypeVoteTypeId
 VTUpMod
CommentsPostId
1. COyeah that helps. Thanks Mike.
 singulars
 PostPostId
 PO
 UserUserId
 USNavaneeth K N

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.