From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Mini ray tracer
Date: Thu, 16 Jun 2005 07:20:41 +0100 [thread overview]
Message-ID: <200506160720.41452.jon@ffconsultancy.com> (raw)
In-Reply-To: <9bbd2794050612202412a79ed2@mail.gmail.com>
On Monday 13 June 2005 04:24, Alex Goldman wrote:
> > 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...
Ahem, it seems that the evil Matthias Blume worked an ingenious bug into his
SML port of my ray tracer which sped it up by 70%. So I've redone the study
and SML is now much less favourable.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2005-06-16 6:21 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 ` [Caml-list] " Alex Goldman
2005-06-16 6:20 ` Jon Harrop [this message]
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=200506160720.41452.jon@ffconsultancy.com \
--to=jon@ffconsultancy.com \
--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).