StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
3398066
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2010-08-03T15:28:48.183
FavoriteCount
0
LastActivityDate
2012-04-11T02:22:04.773
LastEditDate
2012-04-11T02:22:04.773
LastEditorUserId
106797
OwnerUserId
409701
ParentId
1851315
PostTypeId
2
Score
7
ViewCount
0
LastEditorDisplayName
text
Body
I've been working on this issue and i've somewhat succeeded to make the boost interpreter accept the member function such as: <pre><code>// Registers a function with the interpreter, // will not compile if it's a member function. template<typename Function> typename boost::enable_if< ft::is_nonmember_callable_builtin<Function> >::type register_function(std::string const& name, Function f); // Registers a member function with the interpreter. // Will not compile if it's a non-member function. template<typename Function, typename TheClass> typename boost::enable_if< ft::is_member_function_pointer<Function> >::type register_function(std::string const& name, Function f, TheClass* theclass); </code></pre> The enable_if statement is used to prevent the use of the wrong method at the compile time. Now, what you need to understand : <ul> <li>It uses the boost::mpl to parse trough the argument's parameter types of the callable builtin (which is basically a function pointer)</li> <li>Then, prepares a fusion vector at the compile-time (which is a vector that can stock different objects of different types at the same time)</li> <li>When the mpl is done parsing every arguments, the "parsing" apply method will fork in the "invoke" apply method, following the templates.</li> <li>The main issue is that the first argument of a member callable builtin is the object which holds the called method. </li> <li>As far a I know, the mpl cannot parse the arguments of something else than a callable builtin (i.e A Boost::Bind result)</li> </ul> So, what needs to be done is simply add one step to the "parsing" apply, which would be to add the concerned object to the apply loop! Here it goes: <pre><code>template<typename Function, typename ClassT> typename boost::enable_if< ft::is_member_function_pointer<Function> >::type interpreter::register_function( std::string const& name, Function f, ClassT* theclass); { typedef invoker<Function> invoker; // instantiate and store the invoker by name map_invokers[name] = boost::bind(&invoker::template apply_object<fusion::nil,ClassT> ,f,theclass,_1,fusion::nil()); } </code></pre> in interpreter::invoker <pre><code>template<typename Args, typename TheClass> static inline void apply_object( Function func, TheClass* theclass, parameters_parser & parser, Args const & args) { typedef typename mpl::next<From>::type next_iter_type; typedef interpreter::invoker<Function, next_iter_type, To> invoker; invoker::apply( func, parser, fusion::push_back(args, theclass) ); } </code></pre> This way, it will simply skip the first argument type and parse everything correctly. The method can be called this way: <code>invoker.register_function("SomeMethod",&TheClass::TheMethod,&my_object);</code>
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POBoost's Interpreter.hpp example with class member functions
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USCatskul
UserOwnerUserId
1. USAlexandre Deschamps
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. POBoost's Interpreter.hpp example with class member functions
 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
 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.