From: Erik de Castro Lopo <mle+ocaml@mega-nerd.com>
To: "Vu Ngoc San" <san.vu-ngoc@ujf-grenoble.fr>, caml-list@yquem.inria.fr
Subject: Re: [Caml-list] ANNOUNCE : libsndfile-ocaml alpha
Date: Sun, 31 Dec 2006 08:07:56 +1100 [thread overview]
Message-ID: <20061231080756.66e89d6c.mle+ocaml@mega-nerd.com> (raw)
In-Reply-To: <20061227211046.656615d0.mle+ocaml@mega-nerd.com>
Erik de Castro Lopo wrote:
> Vu Ngoc San wrote:
>
> > haven't had the time to really test it, but it seems to work nicely.
> > Wouldn't it be interesting to optionally create a bigarray instead of an
> > array ?
>
> Wow, I've just looked up the Ocaml bigarray module. I didn't even
> know it existed. I'll take a look at it. It may be a better solution
> than what I have now.
After a more detailed look at this I don't see any advantage to
using the bigarray module.
The C API for libsndfile allows reading data as short, int, float or
double. During reads, libsndfile automatically converts from the
internal data format of the file to the data format requested by the
user.
The trouble interfacing with Ocaml is that Ocaml doesn't support
16 bit shorts, 32 bit ints or 32 bit floats. The only data type that
makes any sense is the Ocaml float type (C double).
So, I'd like to ask, if I provide a bigarray interface, how would it
be used?
Erik
--
+-----------------------------------------------------------+
Erik de Castro Lopo
+-----------------------------------------------------------+
"There are two kinds of large software systems: those that
evolved from small systems and those that don't work."
-- Seen on slashdot.org, then quoted by amk
next prev parent reply other threads:[~2006-12-30 21:08 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-22 4:54 Erik de Castro Lopo
2006-12-27 9:32 ` [Caml-list] " Vu Ngoc San
2006-12-27 10:10 ` Erik de Castro Lopo
2006-12-27 10:42 ` Erik de Castro Lopo
2006-12-30 21:07 ` Erik de Castro Lopo [this message]
2006-12-31 3:31 ` skaller
2006-12-31 4:23 ` Erik de Castro Lopo
2006-12-31 11:08 ` Richard Jones
2006-12-31 22:51 ` Erik de Castro Lopo
2007-01-01 14:53 ` Matthieu Dubuget
2007-01-01 19:58 ` Erik de Castro Lopo
2007-01-02 0:51 ` skaller
2007-01-02 1:14 ` Erik de Castro Lopo
2007-01-02 5:26 ` Erick Tryzelaar
2007-01-02 5:39 ` Erik de Castro Lopo
[not found] ` <1167765505.5341.12.camel@rosella.wigram>
2007-01-02 22:37 ` Erik de Castro Lopo
2007-01-02 23:46 ` Gerd Stolpmann
2007-01-03 1:59 ` Pal-Kristian Engstad
2007-01-03 2:49 ` Markus Mottl
2007-01-02 7:47 ` Christoph Bauer
2006-12-31 19:05 ` skaller
2006-12-31 22:54 ` Erik de Castro Lopo
2007-01-02 10:56 ` Vu Ngoc San
2007-01-02 11:27 ` Erik de Castro Lopo
2007-01-02 19:39 ` David Baelde
2007-01-02 23:04 ` Erik de Castro Lopo
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=20061231080756.66e89d6c.mle+ocaml@mega-nerd.com \
--to=mle+ocaml@mega-nerd.com \
--cc=caml-list@yquem.inria.fr \
--cc=san.vu-ngoc@ujf-grenoble.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