From: Christophe TROESTLER <Christophe.Troestler+ocaml@umons.ac.be>
To: christoph.bauer@lmsintl.com
Cc: OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] C Interface and float record
Date: Tue, 16 Jun 2009 11:44:19 +0200 (CEST) [thread overview]
Message-ID: <20090616.114419.669093565955563034.Christophe.Troestler+ocaml@umons.ac.be> (raw)
In-Reply-To: <BB046CA812535C45BD0029AA9D04BA790656017D@KL-SRV57.lmsintl.com>
On Tue, 16 Jun 2009 10:40:31 +0200, Christoph Bauer wrote:
>
> type t = {
> f1 : float;
> f2 : float;
> f3 : float;
> }
>
> and a external C-function should allocate this as for the result.
>
> Do I have to use
>
> caml_alloc(6, Double_array_tag)
caml_alloc(3 * Double_wosize, Double_array_tag)
would be better (portable between 32 and 64 bits).
C.
next prev parent reply other threads:[~2009-06-16 9:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-16 8:40 Christoph Bauer
2009-06-16 9:44 ` Christophe TROESTLER [this message]
2009-06-16 14:57 ` [Caml-list] " Christoph Bauer
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=20090616.114419.669093565955563034.Christophe.Troestler+ocaml@umons.ac.be \
--to=christophe.troestler+ocaml@umons.ac.be \
--cc=caml-list@inria.fr \
--cc=christoph.bauer@lmsintl.com \
/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).