From: Michael Wohlwend <micha-1@fantasymail.de>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Converting C arrays to Ocaml arrays
Date: Mon, 10 Apr 2006 23:21:11 +0200 [thread overview]
Message-ID: <200604102321.11308.micha-1@fantasymail.de> (raw)
In-Reply-To: <c22844d10604101342t5e5796f1g9618eb9a07cbf658@mail.gmail.com>
On Monday 10 April 2006 22:42, Chris Campbell wrote:
> Is the correct way then to alloc another array, then fill it with the
> pointers in the original array then call caml_alloc_array? That seems
> a bit redundant, although I think I might understand why ocaml ffi
> might ask for this format. Is there a macro to help with this, or a
> better way?
no clue about the OpenGL stuff, but can't you just make a Bigarray of the
c-array? Without copying anything?
cheers
Michael
next prev parent reply other threads:[~2006-04-10 21:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 20:42 Chris Campbell
2006-04-10 21:21 ` Michael Wohlwend [this message]
2006-04-11 3:41 ` [Caml-list] " Jonathan Roewen
2006-04-11 3:46 ` Jonathan Roewen
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=200604102321.11308.micha-1@fantasymail.de \
--to=micha-1@fantasymail.de \
--cc=caml-list@yquem.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;
as well as URLs for NNTP newsgroup(s).