From: Jon Harrop <jon@ffconsultancy.com>
To: caml-list@yquem.inria.fr
Subject: Mini ray tracer
Date: Mon, 13 Jun 2005 03:46:06 +0100 [thread overview]
Message-ID: <200506130346.06550.jon@ffconsultancy.com> (raw)
I've been fiddling with my ray tracer again this weekend. This time I've come
up with a comparison of four different (progressively optimised) versions of
the ray tracer implemented in C++, Java, OCaml and SML:
http://www.ffconsultancy.com/free/ray_tracer/languages.html
OCaml is significantly more concise that the other languages (even SML) but
the big surprise for me was the incredible performance of straightforwardly-
written Mlton-compiled SML, even on AMD64 where it lacks a native code-gen.
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next reply other threads:[~2005-06-13 2:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-13 2:46 Jon Harrop [this message]
2005-06-13 3:24 ` [Caml-list] " Alex Goldman
2005-06-16 6:20 ` Jon Harrop
2005-06-16 15:41 ` Jon Harrop
-- strict thread matches above, loose matches on Subject: below --
2005-04-28 9:37 Jon Harrop
2005-05-02 19:48 ` Julian Brown
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=200506130346.06550.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).