From: Richard Jones <rich@annexia.org>
To: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] C stubs with many args.
Date: Sun, 29 Nov 2009 18:31:11 +0000 [thread overview]
Message-ID: <20091129183111.GA20122@annexia.org> (raw)
In-Reply-To: <4B1293BF.1000300@citycable.ch>
On Sun, Nov 29, 2009 at 04:31:11PM +0100, Guillaume Yziquel wrote:
> I've been trying to follow section 18.1.2 of:
>
> http://caml.inria.fr/pub/docs/manual-ocaml/manual032.html
>
> Unfortunately, I'm a bit confused as to what should the CAMLparam and
> such be for the bytecode stub.
>
> Could someone provide me with an example somewhere?
In case you still have problems, you could look at the code we
autogenerate in libguestfs, eg: ocaml/guestfs_c_actions.c. We
generate bindings for functions that have various numbers of arguments
(up to 9).
Rich.
--
Richard Jones
Red Hat
prev parent reply other threads:[~2009-11-29 18:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-29 15:31 Guillaume Yziquel
2009-11-29 16:28 ` [Caml-list] " Guillaume Yziquel
2009-11-29 18:31 ` Richard Jones [this message]
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=20091129183111.GA20122@annexia.org \
--to=rich@annexia.org \
--cc=caml-list@inria.fr \
--cc=guillaume.yziquel@citycable.ch \
/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