From: skaller <skaller@users.sourceforge.net>
To: Olivier Andrieu <andrieu@ijm.jussieu.fr>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] Automatic wrapper generator
Date: 18 May 2004 20:36:09 +1000 [thread overview]
Message-ID: <1084876569.19838.457.camel@pelican.wigram> (raw)
In-Reply-To: <20040518.112506.73847465.andrieu@ijm.jussieu.fr>
On Tue, 2004-05-18 at 19:25, Olivier Andrieu wrote:
>
> > Here's your chance to get THE LOT in one go.
>
> I really don't buy this. There is just not enough information in the C
> prototypes to give you a reasonable interface for OCaml.
You're right. It doesn't generate an interface
any more 'reasonable' than the C one it is wrapping.
> Or does your
> generator use annotations (like camlIDL does) ?
Not at present, although that will be necessary.
> For instance, consider this prototype:
> int foo (double *, int);
> Even if (double *, int) represents an array and its length, the caml
> interface is not obvious :
> float array -> int -> ... (straightforward mapping)
> float array -> ... (use the array length for the int parameter)
> float array -> pos:int -> len:int -> ... (account for pointer arithmetic)
Yup. So what you actually get 'initially' is:
c_double c_ptr -> c_int -> c_int
Not a single Ocaml native data type is visible.
[Well, we could typemap c_int to 'native_int' since they're
isomorphic by specification, and c_double to float for the same
reason ..]
>In the end you get at best a very low-level bunch of autogenerated
> unsafe externals, that you have to re-wrap in ocaml to get something
> comfortable and/or safe to program with.
That is correct, that's what you get.
(1) It's better than nothing :)
(2) It can be used to build a better interface *in Ocaml*
(3) Once it works, it may be possible to add some annotations
to improve the level of abstraction of the generated interface
--
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:36 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
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 [this message]
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=1084876569.19838.457.camel@pelican.wigram \
--to=skaller@users.sourceforge.net \
--cc=andrieu@ijm.jussieu.fr \
--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