From: Guillaume Yziquel <guillaume.yziquel@citycable.ch>
To: Richard Jones <rich@annexia.org>
Cc: OCaml List <caml-list@inria.fr>
Subject: Re: [Caml-list] Wrapping var_args, or C ... in ocaml?
Date: Sun, 14 Feb 2010 23:46:10 +0100 [thread overview]
Message-ID: <4B787D32.10505@citycable.ch> (raw)
In-Reply-To: <20100214180650.GA22433@annexia.org>
Richard Jones a écrit :
> On Sun, Feb 14, 2010 at 04:46:20PM +0100, Guillaume Yziquel wrote:
>> Hello.
>>
>> I'm currently looking at:
>>
>> http://docs.python.org/c-api/arg.html
>>
>> and I would like to know how to wrap up C functions with va_list of with
>> an ellipsis. Is this documented somewhere, or has someone already done
>> something like this?
>
> It really depends on the function and how it will be used. It
> might translate to any of:
>
> (1) A collection of functions implementing different aspects of the C
> function. eg. The open(2) function in Unix is really a varargs
> function, and depending on whether you want to open a file for input,
> output, create, etc. you'd probably be better off with different
> functions in OCaml. (Unix.openfile does _not_ do this ...)
Not the case.
> (2) A simple list, eg. for a C function that takes a NULL-terminated
> list of strings.
Could be.
> (3) A variant list of variants, or option labels, eg. for a C function
> that takes 'type, value'(s), such TIFFSetField in
> libtiff. (http://www.remotesensing.org/libtiff/man/TIFFSetField.3tiff.html)
No.
> (4) Something very specialized, eg. the 'printw' function in ncurses
> is like printf and so would need quite a tricky implementation in
> OCaml. (Probably best to use ksprintf to convert to a string in OCaml
> and then pass printw ("%s", str) in C).
I do not think so.
> In libguestfs where we autogenerate bindings we avoided varargs
> altogether, because it's hard to map such a concept to all the
> different languages we support.
True.
But, I mean, from the point of view of the ABI, there's not much
trickery in the concept. It looks that it is C that is not mapping the
concept to its fullest potential.
I mean, it seems that varargs means on the receiving end "the number of
arguments you'r giving me, as a function, is not limited", whereas on
the sending end, you hard-code the number of arguments in your C code.
Is there a way to map an OCaml list to an ellipsis? Or is it a C limitation?
--
Guillaume Yziquel
http://yziquel.homelinux.org/
next prev parent reply other threads:[~2010-02-14 22:45 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-14 15:46 Guillaume Yziquel
2010-02-14 18:06 ` [Caml-list] " Richard Jones
2010-02-14 20:26 ` Richard Jones
2010-02-14 22:46 ` Guillaume Yziquel [this message]
2010-02-14 22:59 ` Richard Jones
2010-02-14 23:13 ` Guillaume Yziquel
2010-02-14 23:19 ` Richard Jones
2010-02-15 1:34 ` Guillaume Yziquel
2010-02-15 2:37 ` Thomas Fischbacher
2010-02-14 23:31 ` Richard Jones
2010-02-15 10:16 ` Florent Monnier
[not found] ` <201002151106.23642.fmonnier@linux-nantes.fr.eu.org>
[not found] ` <4B7F3FED.4010100@citycable.ch>
2010-02-20 2:41 ` Guillaume Yziquel
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=4B787D32.10505@citycable.ch \
--to=guillaume.yziquel@citycable.ch \
--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