Also for interactive data massaging and visualization.
From: caml-list-boun...@yquem.inria.fr
[mailto:caml-list-boun...@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
Hello,
2010/11/18 Ashish Agarwal agarwal1...@gmail.com:
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.
On Fri, Nov 19, 2010 at 1:09 PM, David MENTRE dmen...@linux-france.org wrote:
Hello,
2010/11/18 Ashish Agarwal agarwal1...@gmail.com:
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
On Fri, Nov 19, 2010 at 1:24 PM, Hezekiah M. Carty hca...@atmos.umd.eduwrote:
ocamlscript is certainly a wonderful tool, for prototyping and
otherwise. It unfortunately doesn't help specifically with the load
a large file and do something with it case.
Right.
Also, I should mention that a
On Nov 19, 2010, at 19:30 , Ashish Agarwal wrote:
On Fri, Nov 19, 2010 at 1:24 PM, Hezekiah M. Carty hca...@atmos.umd.edu
wrote:
ocamlscript is certainly a wonderful tool, for prototyping and
otherwise. It unfortunately doesn't help specifically with the load
a large file and do
On Wed, Nov 17, 2010 at 3:44 AM, Alain Frisch al...@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
On 11/16/2010 03:52 PM, Benedikt Meurer wrote:
OCamlJit 2.0 was specifically designed for desktop processors and is
not really portable to anything else in its current shape, because
the target audience are people using the interactive top-level and
the byte-code interpreter for rapid
