From: Alex Goldman <alex.gman@gmail.com>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Mini ray tracer
Date: Sun, 12 Jun 2005 20:24:47 -0700 [thread overview]
Message-ID: <9bbd2794050612202412a79ed2@mail.gmail.com> (raw)
In-Reply-To: <200506130346.06550.jon@ffconsultancy.com>
> http://www.ffconsultancy.com/free/ray_tracer/languages.html
Thanks. A lot of very interesting stuff there. I'm surprised that
SMLNJ is as fast as OCamlopt on x86. I thought it had a reputation for
being slow because it's "continuations-based" (or whatever). Java is
the only one bytecode-compiled, so it's also interesting that it's
competitive in speed.
It might be interesting to see how C/C++ does when linked with Boehm's
GC. My own experiments with it impressed me very much.
next prev parent reply other threads:[~2005-06-13 3:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 2:46 Jon Harrop
2005-06-13 3:24 ` Alex Goldman [this message]
2005-06-16 6:20 ` [Caml-list] " Jon Harrop
2005-06-16 15:41 ` Jon Harrop
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=9bbd2794050612202412a79ed2@mail.gmail.com \
--to=alex.gman@gmail.com \
--cc=caml-list@yquem.inria.fr \
--cc=jon@ffconsultancy.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).