From: "Warp" <warplayer@free.fr>
To: caml-list@inria.fr, "Jérôme Marant" <jmarant@nerim.net>
Subject: Re: [Caml-list] Ocaml efficiency
Date: Mon, 22 Apr 2002 21:48:52 +0200 [thread overview]
Message-ID: <00ef01c1ea36$baec81c0$fec20b50@warp> (raw)
In-Reply-To: <873cxqqt1y.fsf@marant.org>
> >> What is the real cost (in CPU) of interfaces to C libraries
> >> since some processing have to be performed in order to convert
> >> lower level types to Caml types?
> >
> > I think, that there is no formal answer to your question.
> > Use profiler to find out the bottleneck...
>
> Sure. But maybe experienced coders have good point of view
> about this.
>
Although that kind of question cannot be really answered - because it
depends of your needs , the usage you're making , your knowledge of the
compiler , etc... - all I can say is that OCaml is fast, fast enough to be
used in many kind of applications, even using bytecode compilation. If you
want some benchwark , you can watch the Doug's Bagley's ones at
http://www.bagley.org/~doug/shootout/
All I can say for sure - to my mind - is that OCaml worth it.
Nicolas Cannasse
www.motion-twin.com
-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
next prev parent reply other threads:[~2002-04-22 19:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-20 10:03 Jérôme Marant
2002-04-20 14:51 ` Vitaly Lugovsky
2002-04-20 15:38 ` Jérôme Marant
2002-04-22 19:48 ` Warp [this message]
2002-04-23 17:29 ` Jérôme Marant
2002-04-24 12:05 ` Xavier Leroy
2002-04-24 16:25 ` Jérôme Marant
2002-04-25 16:17 ` Vitaly Lugovsky
2003-02-17 18:03 Vincent Barichard
2003-02-18 21:25 ` Hans Ole Rafaelsen
2003-02-18 21:32 ` Matt Gushee
2003-02-19 0:57 ` Matt Gushee
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='00ef01c1ea36$baec81c0$fec20b50@warp' \
--to=warplayer@free.fr \
--cc=caml-list@inria.fr \
--cc=jmarant@nerim.net \
/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).