From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: "'Ashish Agarwal'" <agarwal1975@gmail.com>,
"'Alain Frisch'" <alain@frisch.fr>
Cc: <caml-list@yquem.inria.fr>
Subject: RE: [Caml-list] Native toplevel? (was: OCamlJit 2.0)
Date: Sat, 20 Nov 2010 11:49:28 -0000 [thread overview]
Message-ID: <04b901cb88a8$fd8c6170$f8a52450$@com> (raw)
In-Reply-To: <AANLkTikgTjYpRFHezXJbwKNEiLF60HyjiFpLWeP1GFem@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 869 bytes --]
Also for interactive data massaging and visualization.
From: caml-list-bounces@yquem.inria.fr
[mailto:caml-list-bounces@yquem.inria.fr] On Behalf Of Ashish Agarwal
Sent: 18 November 2010 16:50
To: Alain Frisch
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Native toplevel? (was: OCamlJit 2.0)
On Wed, Nov 17, 2010 at 3:44 AM, Alain Frisch <alain@frisch.fr> wrote:
Does performance really matter that much for rapid prototyping/development?
Rapid prototyping for me often involves a couple of lines of code that read
in a very large file and do something with it. I have to keep compiling
these small programs to native code because the performance of the toplevel
is too slow. Then, I have to recompile and re-read the whole file for every
little additional thing I want to compute. A high-performance toplevel would
help in this kind of work.
[-- Attachment #2: Type: text/html, Size: 3608 bytes --]
next prev parent reply other threads:[~2010-11-20 11:49 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-16 14:52 OCamlJit 2.0 Benedikt Meurer
2010-11-16 17:07 ` [Caml-list] " bluestorm
2010-11-16 17:32 ` Benedikt Meurer
2010-11-17 8:44 ` Native toplevel? (was: OCamlJit 2.0) Alain Frisch
2010-11-17 10:46 ` Satoshi Ogasawara
2010-11-17 11:38 ` Sylvain Le Gall
2010-11-17 22:57 ` [Caml-list] Native toplevel? Wojciech Daniel Meyer
2010-11-18 16:49 ` [Caml-list] Native toplevel? (was: OCamlJit 2.0) Ashish Agarwal
2010-11-19 18:09 ` David MENTRE
2010-11-19 18:24 ` Hezekiah M. Carty
2010-11-19 18:30 ` Ashish Agarwal
2010-11-19 18:42 ` Benedikt Meurer
2010-11-20 11:49 ` Jon Harrop [this message]
2010-11-18 18:19 ` Benedikt Meurer
[not found] ` <2025993285.616104.1290144569061.JavaMail.root@zmbs4.inria.fr>
2010-11-19 10:02 ` [Caml-list] Re: Native toplevel? Fabrice Le Fessant
2010-11-19 19:16 ` Benedikt Meurer
2010-11-19 18:43 ` [Caml-list] OCamlJit 2.0 Yoann Padioleau
2010-11-19 19:10 ` Benedikt Meurer
2010-11-20 15:59 ` Yoann Padioleau
2010-11-19 19:46 ` Dario Teixeira
2010-11-19 20:20 ` Yoann Padioleau
2010-11-20 15:19 ` [Was: OCamlJit 2.0] Vincent Balat
2010-11-20 15:42 ` [Caml-list] " Benedikt Meurer
2010-11-20 16:10 ` Yoann Padioleau
2010-11-20 16:25 ` Benedikt Meurer
2010-11-20 17:35 ` Yoann Padioleau
2010-11-20 17:08 ` Jon Harrop
2010-11-20 17:37 ` Yoann Padioleau
2010-11-20 17:48 ` Sylvain Le Gall
2010-11-20 18:51 ` [Caml-list] " Jon Harrop
2010-11-20 18:05 ` [Caml-list] " Jon Harrop
2010-11-20 17:15 ` Gerd Stolpmann
2010-11-23 2:09 ` Elias Gabriel Amaral da Silva
2010-11-24 7:20 ` [Caml-list] OCamlJit 2.0 Alain Frisch
2010-11-24 7:59 ` Yoann Padioleau
2010-11-24 9:04 ` Compiling to Javascript Jerome Vouillon
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='04b901cb88a8$fd8c6170$f8a52450$@com' \
--to=jonathandeanharrop@googlemail.com \
--cc=agarwal1975@gmail.com \
--cc=alain@frisch.fr \
--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