From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: caml-list@yquem.inria.fr
Cc: Basile STARYNKEVITCH <basile@starynkevitch.net>,
Raj Bandyopadhyay <rajb@rice.edu>
Subject: Re: [Caml-list] Native code compile time question
Date: Fri, 5 Sep 2008 23:46:07 +0100 [thread overview]
Message-ID: <200809052346.07765.jon@ffconsultancy.com> (raw)
In-Reply-To: <48C1A56C.4090401@starynkevitch.net>
On Friday 05 September 2008 22:32:28 Basile STARYNKEVITCH wrote:
> It depends of your langage and of the code you are generating, but maybe
> Ocaml is not the right tool for that. Did you consider stuff like LLVM
> http://llvm.org...
FWIW: LLVM and its OCaml bindings are absolutely superb.
--
Dr Jon Harrop, Flying Frog Consultancy Ltd.
http://www.ffconsultancy.com/?e
next prev parent reply other threads:[~2008-09-05 21:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-05 16:26 Raj Bandyopadhyay
2008-09-05 21:32 ` [Caml-list] " Basile STARYNKEVITCH
2008-09-05 22:46 ` Jon Harrop [this message]
2008-09-05 22:44 ` Jon Harrop
2008-09-06 10:01 ` Richard Jones
2008-09-06 10:38 ` Christophe TROESTLER
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=200809052346.07765.jon@ffconsultancy.com \
--to=jonathandeanharrop@googlemail.com \
--cc=basile@starynkevitch.net \
--cc=caml-list@yquem.inria.fr \
--cc=rajb@rice.edu \
/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).