From: Joel Reymont <joelr1@gmail.com>
To: Gabriel Scherer <gabriel.scherer@gmail.com>
Cc: Goswin von Brederlow <goswin-v-b@web.de>, caml-list@inria.fr
Subject: Re: [Caml-list] using modules to wrap c++ classes
Date: Thu, 3 May 2012 20:20:42 +0100 [thread overview]
Message-ID: <CAOQwdX0bxBR5OUwWQQ6LuLt6Wf6Qg8iPcgK2XnDf2A78A6nHbQ@mail.gmail.com> (raw)
In-Reply-To: <CAOQwdX0Hap02NZMW53Mx-bUiP3tOUZPH6tUYQv7fWY3EdSjdcQ@mail.gmail.com>
I'm doing this to dispatch callbacks on the C side.
Are there any issues with doing it this way?
Is there a better way?
Thanks, Joel
---
enum
{
ALERT
};
static CAMLprim value callbacks[] =
{
Val_unit // Alert
};
template<class T>
inline void dispatch(CAMLprim value (*make)(T*), value v, T* p, void* ctx)
{
if (v != Val_unit)
{
caml_c_thread_register();
CAMLlocal1(o);
o = make(p);
callback2(v, (value)ctx, o);
}
}
class MyAdmCallbacks: public AdmCallbacks
{
public :
MyAdmCallbacks() {};
~MyAdmCallbacks() {};
virtual int Alert(AlertInfo* pInfo, void* pContext, int* aiCode)
{
dispatch(Alert_new_from, callbacks[ALERT], pInfo, pContext);
*aiCode = API_OK;
return (OK);
}
};
--------------------------------------------------------------------------
Working on AlgoKit, a new algorithmic trading platform using Rithmic R|API
---------------------+------------+---------------------------------------
http://wagerlabs.com | @wagerlabs | http://www.linkedin.com/in/joelreymont
---------------------+------------+---------------------------------------
next prev parent reply other threads:[~2012-05-03 19:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 12:22 Joel Reymont
2012-05-03 13:35 ` Goswin von Brederlow
2012-05-03 13:56 ` Joel Reymont
2012-05-03 14:27 ` Gabriel Scherer
2012-05-03 15:02 ` Joel Reymont
2012-05-03 18:41 ` Joel Reymont
2012-05-03 19:20 ` Joel Reymont [this message]
2012-05-04 8:43 ` Goswin von Brederlow
2012-05-04 17:23 ` Joel Reymont
2012-05-05 12:39 ` Goswin von Brederlow
2012-05-05 14:11 ` Joel Reymont
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOQwdX0bxBR5OUwWQQ6LuLt6Wf6Qg8iPcgK2XnDf2A78A6nHbQ@mail.gmail.com \
--to=joelr1@gmail.com \
--cc=caml-list@inria.fr \
--cc=gabriel.scherer@gmail.com \
--cc=goswin-v-b@web.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).