caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Ville-Pertti Keinonen <will@exomi.com>
To: Oleg Trott <oleg_trott@columbia.edu>
Cc: Michael Vanier <mvanier@cs.caltech.edu>,
	skaller@users.sourceforge.net, caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] extensible records again
Date: Mon, 22 Mar 2004 09:49:54 +0200	[thread overview]
Message-ID: <819CA932-7BD5-11D8-9C9B-000393863F70@exomi.com> (raw)
In-Reply-To: <405DD298.109@columbia.edu>


On Mar 21, 2004, at 7:36 PM, Oleg Trott wrote:

> If I were writing a dynamically-typed language implementation in 
> O'Caml, I'd _compile_ it _to_ O'Caml (as opposed to interpreting the 
> language) In fact, except for EVAL and CALL/CC, it's probably very 
> trivial to write a Scheme-to-OCaml compiler, and get the performance 
> on par with decent native-code Scheme compilers.

How would you handle interactive sessions?

Anyway, I'm pretty sure call/cc is far easier than getting good 
performance, all you need to do is use CPS, which is simple and 
efficient in OCaml.  If you want the code to run fast, you need to do 
something to make function calls more direct (no lists or arrays of 
arguments)...

The native-code Scheme compilers I've tried aren't too impressive, they 
can produce fast code but not safely and/or not with the full language 
semantics, one of the things restricting them is using C as an 
intermediate language (OCaml as an intermediate language would suffer 
from most of the same problems).  Decent Common Lisp systems work far 
better, producing native code directly, even in interactive sessions.

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


  parent reply	other threads:[~2004-03-22  7:49 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-21  6:21 Michael Vanier
2004-03-21  8:08 ` Oleg Trott
2004-03-21  8:40   ` Michael Vanier
2004-03-21 16:10     ` Oleg Trott
2004-03-21 17:06       ` skaller
2004-03-21 17:36         ` Oleg Trott
2004-03-22  3:19           ` skaller
2004-03-22  7:49           ` Ville-Pertti Keinonen [this message]
2004-03-22  9:32             ` Oleg Trott
2004-03-22 10:25               ` Ville-Pertti Keinonen
2004-03-21 22:35         ` Michael Vanier
2004-03-22  3:39           ` skaller
2004-03-21 22:34       ` Michael Vanier
2004-03-22  3:31         ` skaller
2004-03-22  5:54           ` Michael Vanier
2004-03-23 19:14             ` skaller
2004-03-24  1:41               ` Jacques Garrigue
2004-03-24  8:44                 ` Julien Signoles
2004-03-24 10:04                   ` Jacques Garrigue
2004-03-21  8:53 ` Martin Jambon
2004-03-21  9:22   ` Michael Vanier
2004-03-21 17:00 ` skaller
2004-03-22  8:13 ` Achim Blumensath
2004-03-23  2:14   ` Michael Vanier
2004-03-23  7:25     ` Achim Blumensath
2004-03-31 10:05 ` Marcin 'Qrczak' Kowalczyk

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=819CA932-7BD5-11D8-9C9B-000393863F70@exomi.com \
    --to=will@exomi.com \
    --cc=caml-list@inria.fr \
    --cc=mvanier@cs.caltech.edu \
    --cc=oleg_trott@columbia.edu \
    --cc=skaller@users.sourceforge.net \
    /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).