StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
10291739
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
3
CommunityOwnedDate
CreationDate
2012-04-24T04:26:27.713
FavoriteCount
0
LastActivityDate
2012-04-24T10:39:08.720
LastEditDate
2017-05-23T12:01:53.873
LastEditorUserId
-1
OwnerUserId
78845
ParentId
10291467
PostTypeId
2
Score
2
ViewCount
0
LastEditorDisplayName
text
Body
You should read <a href="https://stackoverflow.com/questions/3381829/how-do-i-implement-a-callback-in-c">How do I implement a callback in C++?</a> and pay particular attention to references to the <a href="http://en.wikipedia.org/wiki/Observer_pattern" rel="nofollow noreferrer">Observer Pattern</a>. If you have two such tightly-coupled classes then you probably want to re-think your design as testing them will soon become a nightmare. That said, here is how to finish the implementation that you started... <pre><code>#include <iostream> class First; // Typedefs make this much more readable: http://www.parashift.com/c++-faq-lite/pointers-to-members.html#faq-33.5 typedef void (First::*SecondTriggeredCallback)(void); // And macros make the call much more readable: http://www.parashift.com/c++-faq-lite/pointers-to-members.html#faq-33.6 #define CALL_MEMBER_FN(object, ptrToMember) ((object).*(ptrToMember)) class Second { public: // You'll also need an *instance* of the First class Second(SecondTriggeredCallback SecondTriggered, First& first) { CALL_MEMBER_FN(first, SecondTriggered)(); } }; class First { private: Second *second; public: First() { std::cout << "first class was created" << std::endl; second = new Second(&First::SecondTriggered, *this); } ~First() { delete second; } void SecondTriggered() { std::cout << "second class was created and responded" << std::endl; } }; int main() { First first; } </code></pre> <a href="http://ideone.com/7USO1" rel="nofollow noreferrer">See it run</a>! <hr> Here's a version that removes the coupling by using templates: <pre><code>#include <iostream> // Macros make the call much more readable: http://www.parashift.com/c++-faq-lite/pointers-to-members.html#faq-33.6 #define CALL_MEMBER_FN(object, ptrToMember) ((object).*(ptrToMember)) template <class T> struct Second { // Typedefs make this much more readable: http://www.parashift.com/c++-faq-lite/pointers-to-members.html#faq-33.5 typedef void (T::*SecondTriggeredCallback)(void); // You'll also need an *instance* of the "T" class Second(SecondTriggeredCallback SecondTriggered, T& t) { CALL_MEMBER_FN(t, SecondTriggered)(); } }; class First { public: First() :second(NULL) { std::cout << "first class was created" << std::endl; second = new Second<First>(&First::SecondTriggered, *this); } ~First() { delete second; } void SecondTriggered() { std::cout << "second class was created and responded" << std::endl; } private: First(const First&); First& operator =(const First&); Second<First>* second; }; int main() { First first; } </code></pre>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POPassing data between classes with function pointers
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCommunity
UserOwnerUserId
1. USJohnsyweb
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

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.