From: skaller <skaller@users.sourceforge.net>
To: Richard Jones <rich@annexia.org>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Automatic wrapper generator
Date: 18 May 2004 20:07:48 +1000 [thread overview]
Message-ID: <1084874867.19838.427.camel@pelican.wigram> (raw)
In-Reply-To: <20040518085805.GB15477@redhat.com>
On Tue, 2004-05-18 at 18:58, Richard Jones wrote:
> John,
>
> This is of course brilliant news if it can be made to work.
I think it can be "made" to work. By 'made' I mean: C headers
are relatively unstructured hacks, some important header
files actually contain *syntax* errors for example!
So it is to be expected the client will need to apply some
directives to guide the wrapping, so as to 'undo' the C hackery
if you like.
> I can
> help you with testing - I've got a few different platforms around
> here.
Great! Note: there is currently no Ocaml back end.
> I'm interested to know, though: how do you deal with ownership of
> objects: eg. The struct returned from gethostbyname(3) is static and
> so shouldn't be managed/freed from OCaml; whereas getnameinfo(3)
> requires you to pass in allocated buffers and their sizes. This
> information isn't available in the header files ...
Simple. I don't. For a low level C interface, everything
works exactly 'as if in C'. If you need to create a string
you call 'malloc' and 'strcpy', just as in C.
So, if there is a static data structure and you call
a function that returns it, you have to manage
it from Felix or Ocaml exactly as in C: don't free it
or you'll core dump.
Note that this couldn't possibly work in Ocaml except
that the garbage collector is smart and *knows* which
pointers to leave alone. Those pointers you manage
'just as you would do in C'.
--
John Skaller, mailto:skaller@users.sf.net
voice: 061-2-9660-0850,
snail: PO BOX 401 Glebe NSW 2037 Australia
Checkout the Felix programming language http://felix.sf.net
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2004-05-18 10:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 8:38 skaller
2004-05-18 8:58 ` Richard Jones
2004-05-18 10:07 ` skaller [this message]
2004-05-18 9:06 ` Basile Starynkevitch local
2004-05-18 10:25 ` skaller
2004-05-18 12:11 ` Richard Jones
2004-05-18 17:21 ` Michael Hamburg
2004-05-18 18:34 ` skaller
2004-05-18 19:27 ` Richard Jones
2004-05-18 20:52 ` skaller
2004-05-18 20:02 ` Gerd Stolpmann
2004-05-18 20:10 ` [Caml-list] Functional critical section SWAMPY
2004-05-18 20:31 ` Kenneth Knowles
2004-05-18 20:39 ` Evan Martin
2004-05-19 7:35 ` thornber
2004-05-19 7:33 ` thornber
2004-05-18 9:25 ` [Caml-list] Automatic wrapper generator Olivier Andrieu
2004-05-18 10:36 ` skaller
2004-05-18 9:38 ` Fermin Reig
2004-05-18 10:42 ` skaller
2004-05-18 10:57 ` Felix Winkelmann
2004-05-18 10:58 ` John Chu
2004-05-18 11:33 ` skaller
2004-05-22 10:09 ` Marcin 'Qrczak' Kowalczyk
2004-05-22 13:13 ` skaller
2004-05-22 14:19 ` Marcin 'Qrczak' Kowalczyk
2004-05-22 16:14 ` skaller
2004-05-23 10:58 ` Marcin 'Qrczak' Kowalczyk
2004-05-23 19:59 ` skaller
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=1084874867.19838.427.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=caml-list@inria.fr \
--cc=rich@annexia.org \
/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