From: skaller <skaller@users.sourceforge.net>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Re: Ocaml for Scientific computing
Date: Wed, 26 Sep 2007 07:01:14 +1000 [thread overview]
Message-ID: <1190754074.6800.8.camel@rosella.wigram> (raw)
In-Reply-To: <200709252138.49050.jon@ffconsultancy.com>
On Tue, 2007-09-25 at 21:38 +0100, Jon Harrop wrote:
> I'm not sure that it is conceptually more difficult to do similar things for
> OCaml but my vote goes to hoisting bounds checks. I don't like having to
> write unsafe code by hand in OCaml and F# does a great job of improving
> performance by hoisting bounds checks.
I guess that this is easier. How much speed is gained eliding
bounds checks?
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-09-25 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-25 17:27 Mike Lin
2007-09-25 18:46 ` [Caml-list] " skaller
2007-09-25 20:38 ` Jon Harrop
2007-09-25 21:01 ` skaller [this message]
2007-09-26 8:27 ` Florian Hars
2007-09-26 8:53 ` skaller
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=1190754074.6800.8.camel@rosella.wigram \
--to=skaller@users.sourceforge.net \
--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).