StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
12597817
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
1
CommunityOwnedDate
CreationDate
2012-09-26T08:43:28.260
FavoriteCount
0
LastActivityDate
2012-09-26T12:37:39.707
LastEditDate
2012-09-26T12:37:39.707
LastEditorUserId
710388
OwnerUserId
710388
ParentId
12577970
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
You might try that solution (a little bit hacky, but I think, it should work for you): <pre><code>void fortranFunction(int n, void udf(double*)) { double d = static_cast<double>(n); udf(&d); } class myClass { public: void classUDF(double* a) { } }; #ifdef _MSC_VER #define THREADLOCALSTATIC __declspec(thread) static #define THREADLOCAL #else #define THREADLOCALSTATIC static ___thread #define THREADLOCAL ___thread #endif struct _trampolinebase { THREADLOCALSTATIC _trampolinebase* current_trampoline; }; THREADLOCAL _trampolinebase* _trampolinebase::current_trampoline = 0; #undef THREADLOCAL #undef THREADLOCALSTATIC template<class CBRET, class CBARG1, class T> struct _trampoline1 : _trampolinebase { typedef CBRET (T::*CALLBACKFN)(CBARG1); _trampoline1(T& target, CALLBACKFN& callback) : callback_(callback) , target_(target) { assert(current_trampoline == 0); current_trampoline = this; } static CBRET callback(CBARG1 a1) { _trampoline1* this_ = static_cast<_trampoline1*>(current_trampoline); current_trampoline = 0; return this_->trampoline(a1); } private: CBRET trampoline(CBARG1 a1) { return (target_.*callback_)(a1); } CALLBACKFN& callback_; T& target_; }; template<class FRET, class FARG1, class CBRET, class CBARG1, class T, class F> FRET call1_1(T& target, CBRET (T::*callback)(CBARG1), F& fortranfunction, FARG1 a) { typedef typename _trampoline1<CBRET, CBARG1, T> trampoline; trampoline t(target, callback); return fortranFunction(a, trampoline::callback); } int main() { int n=1; myClass myClassObj; call1_1<void,int,void,double*>(myClassObj, &myClass::classUDF, fortranFunction, 1); } </code></pre> With the 'threadlocal' stuff, this will work in multithreaded calls, too. You may omit that, if you don't use a multithreaded environment. It also works with recursive calls (e.g. if the callback calls another fortran function). This solution works only for one single argument plus callback for the fortran function and one single argument in the callback function itself, but you should be able to extend it easily. This is also, why I called it 'call1_1' (fortran function with 1 argument, callbackfunction with 1 argument). FRET is the return type of the fortran function, FARG1 the type of the first argument (int in this case). CBRET and CBARG are the same for the callback function. Before the fortran function is actually called, the target object is stored within a global (thread-local) variable. The fortran function calls a static callback function, which finally calls your member function. I invented the trampolinebase to instantiate the static member, I could also have used a global variable for that (but for some reason, I don't like global variables too much) ;-)
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POC++ class member callback and external library
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USMark
UserOwnerUserId
1. USMark
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. CONote, that this will only work, if the callback function is called from the fortran function itself. It won't work, if the callback is stored within the fortran code and called _after_ the fortran call returns.
 singulars
 PostPostId
 PO
 UserUserId
 USMark

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.