From: STARYNKEVITCH Basile <Basile.Starynkevitch@cea.fr>
To: "Mattias Waldau" <mattias.waldau@tacton.se>
Cc: "OCAML" <caml-list@inria.fr>
Subject: RE: JIT-compilation for OCaml?
Date: Wed, 3 Jan 2001 15:40:32 +0100 [thread overview]
Message-ID: <14931.14816.249732.816455@gargle.gargle.HOWL> (raw)
In-Reply-To: <HDEEKOMJILGEIHIMAPCDGEPFDMAA.mattias.waldau@tacton.se>
>>>>> "Mattias" == Mattias Waldau <mattias.waldau@tacton.se> writes:
Mattias> If you just want portability, then why not generate
Mattias> Java-byte code instead of Ocaml-bytecode.
It is well known (e.g. see the Kawa implementation of Scheme on the
JVM) that the Java Virtual Machine is not well suited for functional
programming: function closures and tail-recursion calls (which are
actually jump with arguments) do not exist in the JVM, and emulating
them (e.g. closures as instances of specially generated classes) is
quite inefficient. The JVM is not as universal as Sun's marketing hype
claim it is...
On the contrary the Ocaml virtual machine was (of course) designed for
functional programming, and efficiently implement tails calls and
closure constructions.
Regards and Happy New Year to all,
N.B. Any opinions expressed here are only mine, and not of my organization.
N.B. Les opinions exprimees ici me sont personnelles et n engagent pas le CEA.
---------------------------------------------------------------------
Basile STARYNKEVITCH ---- Commissariat à l Energie Atomique
DTA/LETI/DEIN/SLA * CEA/Saclay b.528 (p111f) * 91191 GIF/YVETTE CEDEX * France
phone: 1,69.08.60.55; fax: 1.69.08.83.95 home: 1,46.65.45.53
email: Basile point Starynkevitch at cea point fr
web perso: http://perso.wanadoo.fr/starynkevitch/basile/
next prev parent reply other threads:[~2001-01-04 13:05 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-02 16:07 Markus Mottl
2001-01-02 18:16 ` Mattias Waldau
2001-01-02 19:30 ` Markus Mottl
2001-01-03 12:15 ` Alain Frisch
2001-01-04 8:37 ` Fabrice Le Fessant
2001-01-04 9:04 ` Alain Frisch
2001-01-03 13:23 ` Mattias Waldau
2001-01-03 14:25 ` Markus Mottl
2001-01-03 14:40 ` STARYNKEVITCH Basile [this message]
2001-01-03 15:51 ` John Max Skaller
2001-01-03 17:50 ` Markus Mottl
2001-01-05 0:30 ` Michael Hicks
2001-01-08 9:59 ` Xavier Leroy
2001-01-09 6:40 ` John Max Skaller
2001-01-03 17:49 ` Joseph R. Kiniry
2001-01-03 18:19 ` Markus Mottl
2001-01-03 18:38 ` Joseph R. Kiniry
2001-01-03 18:58 ` Markus Mottl
2001-01-03 19:06 ` Joseph R. Kiniry
2001-01-04 22:32 ` Jonathan Coupe
2001-01-07 0:16 ` Chris Hecker
2001-01-05 12:52 ` Sven LUTHER
2001-01-05 20:08 ` Joseph R. Kiniry
2001-01-09 7:14 ` John Max Skaller
2001-01-09 6:50 ` John Max Skaller
2001-01-05 12:39 ` Sven LUTHER
2001-01-05 5:48 ` Vitaly Lugovsky
2001-01-03 15:24 Jerry Jackson
2001-01-04 14:12 ` Alan Schmitt
2001-01-09 17:09 Dave Berry
2001-01-11 6:38 ` John Max Skaller
2001-01-09 17:18 Dave Berry
2001-01-11 7:00 ` John Max Skaller
2001-01-11 10:01 ` Alain Frisch
2001-01-12 7:55 ` John Max Skaller
2001-01-11 12:45 Dave Berry
2001-01-12 8:23 ` John Max Skaller
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=14931.14816.249732.816455@gargle.gargle.HOWL \
--to=basile.starynkevitch@cea.fr \
--cc=caml-list@inria.fr \
--cc=mattias.waldau@tacton.se \
/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).