From: Dmitry Bely <dmitry.bely@gmail.com>
To: Caml List <caml-list@inria.fr>
Subject: Re: [Caml-list] C wrappers for Ocaml functions
Date: Tue, 14 Apr 2009 18:06:07 +0400 [thread overview]
Message-ID: <90823c940904140706i512e4fe0o1d223ec77d6bf478@mail.gmail.com> (raw)
In-Reply-To: <9af41d0e0904140451l5a3a0207vb5bd7532a35bbc4e@mail.gmail.com>
On Tue, Apr 14, 2009 at 3:51 PM, Tim Leek <trleek@gmail.com> wrote:
> Hello. Not sure if this should have gone to beginners or the regular
> list. Also not sure if its been answered before. If so, please
> redirect me! I did a bunch of searching both on google and in the lists
> and couldn't find the answers I needed. So here goes.
>
> I have written a blob of code in Ocaml that I like very much. I'd love
> to keep it in ocaml and not have to worry about things like memory leaks
> and so on. However, much of what I do is in C and can't be in Ocaml.
> So I am investigating packing my nice Ocaml code into a library and
> writing C bindings so that I can talk to it.
>
> Virtually all of the tutorials out there and documentation cover how to
> create Ocaml bindings to a C library. I don't want to do that. The few
> examples I have found that are relevant are toy ones. How to write C
> bindings to an Ocaml "fib" function, e.g. In particular, I have found
> none that cover how to obtain pointers to OCaml function return values
> that are not strings or ints, how to store them in C-land, and how to pass
> them back to Ocaml as parameters.
>
> Let's take as a concrete example the following: creating C bindings for
> a simple hash table mapping string keys to integer values. If I can
> generate bindings for this that work I should be able to do so for the
> library I really care about.
>
> Here's what I put together for the hash table slightly-less-than-toy
> example. It doesn't even compile. [Oddly, with very similar incantations
> my own code does compiles but then segfaults inside one of the Ocaml fns.]
> Any help much appreciated!
>
> -Tim
>
>
> 1. The implementation.
>
> % cat ht.ml
>
> type ht = (string,int) Hashtbl.t
>
> let create () : ht = Hashtbl.create 100
>
> let add (table:ht) key valu = Hashtbl.add table key valu
>
> let mem (table:ht) key = Hashtbl.mem table key
>
> let remove (table:ht) key = if (Hashtbl.mem table key) then
> Hashtbl.remove table key
>
> let _ = Callback.register "create" create
>
> let _ = Callback.register "add" add
>
> let _ = Callback.register "mem" mem
>
> let _ = Callback.register "remove" remove
>
> 2. The wrappers
>
> % cat ht_wrap.c
> #include <caml/mlvalues.h>
> #include <caml/callback.h>
> #include <caml/alloc.h>
>
> void *ht_create (void) {
> static value *create_closure = NULL;
> if (create_closure == NULL)
> create_closure = caml_named_value("create");
> return ((void *) (caml_callback(*create_
> closure, Val_unit)));
> }
>
> void ht_add (void *ht, char *key, int val) {
> static value *add_closure = NULL;
> if (add_closure == NULL)
> add_closure = caml_named_value("add");
> caml_callback3(*add_closure, (value) ht, caml_copy_string(key),
> Val_int(val));
> }
>
> void ht_mem (void *ht, char *key) {
> static value *mem_closure = NULL;
> if (mem_closure == NULL)
> mem_closure = caml_named_value("mem");
> caml_callback2(*mem_closure, (value) ht, caml_copy_string(key));
> }
>
> void ht_remove (void *ht, char *key) {
> static value *remove_closure = NULL;
> if (remove_closure == NULL)
> remove_closure = caml_named_value("remove");
> caml_callback2(*remove_closure, (value) ht, caml_copy_string(key));
> }
>
>
> 3. Header file for those wrappers
>
> % cat ht.h
>
> void *ht_create (void);
> void ht_add (void *ht, char *key, int val);
> void ht_mem (void *ht, char *key);
> void ht_remove (void *ht, char *key);
>
> 4. The test program, with main() function.
>
> % cat ht_test.c
> #include <stdio.h>
> #include "ht.h"
>
> int main (int argc, char **argv) {
> void *ht;
>
> caml_startup(argv);
>
> ht = ht_create();
> ht_add(ht, "foo", 1);
> ht_add(ht, "foo", 1);
> ht_add(ht, "bar", 1);
> ht_remove(ht, "foo");
> }
>
>
> 5. And this is how I am attempting to compile it. Note that error I'm
> getting here is in link. If I add "-lm" it gets less noisy but still is
> mad at me. Why am I having to add math library? Again, help!!
>
> % ocamlopt -output-obj -o ht.o ht.ml
Wrong! You cannot specify ht.o as an output as ht.o is an intermediate
result of ht.ml compilation. Activate -verbose flag and you'll see.
Replace it with something like
ocamlopt -output-obj -o ht_out.o ht.ml
> % ocamlopt -c ht_wrap.c
> % cp /usr/lib/ocaml/3.10.0/libasmrun.a ./ht.a
> % ar r ht.a ht_wrap.o ht.o
> % gcc -o htt ht_test.c ht.a -lcurses
> ht.a(floats.o): In function `caml_ceil_float':
> (.text+0x193): undefined reference to `ceil'
> ht.a(floats.o): In function `caml_atan2_float':
> (.text+0x1ae): undefined reference to `atan2'
(...)
Why simply not to use
ocamlopt -c ht_wrap.c
gcc -o htt ht_test.c ht_out.o ht_wrap.o -L${OCAMLLIB} -lasmrun -lcurses -lm
?
- Dmitry Bely
next prev parent reply other threads:[~2009-04-14 14:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 11:51 Tim Leek
2009-04-14 14:06 ` Dmitry Bely [this message]
2009-04-14 14:40 ` [Caml-list] " Xavier Leroy
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=90823c940904140706i512e4fe0o1d223ec77d6bf478@mail.gmail.com \
--to=dmitry.bely@gmail.com \
--cc=caml-list@inria.fr \
/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