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: 19 May 2004 06:52:16 +1000 [thread overview]
Message-ID: <1084913536.19838.688.camel@pelican.wigram> (raw)
In-Reply-To: <20040518192708.GA29803@redhat.com>
On Wed, 2004-05-19 at 05:27, Richard Jones wrote:
> I think your analysis is correct, except that you've missed out C
> macros. Both the Perl and Gtk C interfaces use macros all over the
> place as a kind of inline function.
Flxcc currently forgets all about macros.
I'm not totally unhappy :)
You may have to call __f instead of f.
That's not quite as bad as losing M_PI out of math.h though.
To fix this I'd need a C preprocessor to modify,
and probably also some annotations to help chose
the macros to export as part of the interface.
They'd have to be typed.. which isn't so easy if the macros
are used as generics.
Felix itself has no problem with binding macros,
including generic ones (just cheat a bit and pretend
they're really parametrically polymorphic).
Note I haven't forgotten them. Indeed one of my main
reasons for abandoning SWIG was that it doesn't
provide any hooks to catch macros intended as
functions. (It catches constants automatically though).
The bottom line is that if you want to make a wrapper
that conforms to a well specified (documented) interface,
you should do it 'by hand' or by processing the documentation,
not by processing the source code. Of course probably
the fastest way to do this is to patch up a flxcc generated
wrapper.. :)
--
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 20:52 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 [this message]
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=1084913536.19838.688.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;
as well as URLs for NNTP newsgroup(s).