From: "Evan Martin" <martine@danga.com>
To: Elthariel <elthariel@free.fr>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Could be Caml a good language for sound manipulation ?
Date: Sun, 28 Nov 2004 19:35:26 -0800 [thread overview]
Message-ID: <20041129033526.GA45540@trout> (raw)
In-Reply-To: <41AA5C8C.2010503@free.fr>
On Mon, Nov 29, 2004 at 12:17:32AM +0100, Elthariel wrote:
> I'm quite new in oCaml world, I partially learnt it in my school (EPITA
> / Paris) and I'm going to finish this next year. I'm not really ease in
> english so my question will be short : do you think Caml coul be a nice
> langage for sound manipulation implementation, as Synthetizers, effects
> plugins ? I doesn't ask for answer in term of performance which should
> be I guess quite good :p, but more in term of software design and
> language facility.
The main problem I've encountered is that if you allocate memory while
processing large streams of data, your program ends up spending a lot of
its processing time in the garbage collector.
--
Evan Martin
martine@danga.com
http://neugierig.org
prev parent reply other threads:[~2004-11-29 3:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-28 23:17 Elthariel
2004-11-29 3:21 ` Julian Brown
2004-11-29 3:35 ` Evan Martin [this message]
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=20041129033526.GA45540@trout \
--to=martine@danga.com \
--cc=caml-list@yquem.inria.fr \
--cc=elthariel@free.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