From: skaller <skaller@users.sourceforge.net>
To: Jon Harrop <jon@ffconsultancy.com>
Cc: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] Dynamic linking
Date: Sun, 17 Jun 2007 03:59:33 +1000 [thread overview]
Message-ID: <1182016773.553.64.camel@rosella.wigram> (raw)
In-Reply-To: <200706161833.32255.jon@ffconsultancy.com>
On Sat, 2007-06-16 at 18:33 +0100, Jon Harrop wrote:
> On Friday 15 June 2007 19:24:20 Alain Frisch wrote:
> > Except for the native toplevel which will probably not be included.
>
> The native top-level is the bit that interests me the most, as this combines
> interactivity with OCaml's superb native-code performance.
I do not understand how the toplevel is even remotely useful:
it isn't "interactive" in any real sense of the word.
Natively you can't even edit lines, it's very lame.
Even with ledit, what you can do is very limited.
I fail to see how this is any better than preparing
a file and compiling it -- that way you get a proper
editor. If you're using emacs or some other souped up
editor it works much like an interactive IDE anyhow,
only better..
So exactly what is the advantage of the top level?
Yes, I use it occasionally for testing 1-2 line
fragments, mainly the typing, but i just can't
envisage how a ray tracer could be use productively
in such an environment, as compared to just making
a suitable file and compiling and running it.
It IS a bit of a pain, setting up the build environment
to do that, but I can't imagine it's that hard to automate
with something like emacs, or one of the make systems.
--
John Skaller <skaller at users dot sf dot net>
Felix, successor to C++: http://felix.sf.net
next prev parent reply other threads:[~2007-06-16 17:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-15 16:03 Alain Frisch
2007-06-15 16:47 ` [Caml-list] " Joel Reymont
2007-06-15 16:52 ` Brian Hurt
2007-06-15 18:24 ` Alain Frisch
2007-06-15 18:59 ` Jon Harrop
2007-06-15 20:57 ` Alain Frisch
2007-06-15 22:38 ` Quôc Peyrot
2007-06-16 7:23 ` Alain Frisch
2007-06-16 17:33 ` Jon Harrop
2007-06-16 17:59 ` skaller [this message]
2007-06-16 20:13 ` Christophe TROESTLER
2007-06-16 23:10 ` Philippe Wang
2007-06-15 22:37 ` skaller
2007-06-15 22:45 ` Christophe TROESTLER
2007-06-15 22:58 ` skaller
2007-06-20 13:40 ` Alain Frisch
2007-06-24 11:35 ` Jon Harrop
-- strict thread matches above, loose matches on Subject: below --
2007-06-18 4:18 Jeffrey Loren Shaw
2005-10-05 13:11 Alexander Bottema
2005-10-04 15:56 Alexander Bottema
2005-10-05 8:14 ` skaller
2005-10-04 12:47 Alexander Bottema
2005-10-04 14:47 ` skaller
2005-09-28 12:44 Alexander Bottema
2005-09-26 3:09 Jonathan Roewen
2005-09-26 4:26 ` skaller
2005-09-26 5:14 ` Jacques Garrigue
2005-09-26 5:20 ` Jonathan Roewen
2005-09-28 9:05 ` Jacques Garrigue
2005-04-05 21:12 Emir Pasalic
2005-04-05 22:02 ` [Caml-list] " Igor Pechtchanski
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=1182016773.553.64.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