caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Michael Hicks <mwh@dsl.cis.upenn.edu>
To: mottl@miss.wu-wien.ac.at (Markus Mottl)
Cc: skaller@ozemail.com.au, mattias.waldau@abc.se, caml-list@inria.fr
Subject: Re: JIT-compilation for OCaml?
Date: Thu, 4 Jan 2001 19:30:36 -0500 (EST)	[thread overview]
Message-ID: <200101050030.f050Uas06293@codex.cis.upenn.edu> (raw)
In-Reply-To: <20010103185023.A29666@miss.wu-wien.ac.at> from "Markus Mottl" at Jan 3, 2001 06:50:23 pm

> On Thu, 04 Jan 2001, John Max Skaller wrote:
> > 	Actually, I think ocamlopt is _more_ portable.
> > There's no mucking around with custom run-times, etc.
> 
> Well, it would be really funny to see OCaml compete against Java in
> the browser market (a rather unrealistic dream, I fear). Wasn't there a
> basic WWW-browser written in OCaml? I am not sure, but I think it also
> supported OCaml-byte code.

MMM, the Ocaml-based web browser, still exists, see
http://caml.inria.fr/archives/200005/msg00082.html.  However, last I knew,
the Ocaml bytecode lacks the security guarantees of Java bytecode.  Dynamic
linking will not violate stated interface constraints, but these can be
spoofed, I believe.  

Mike

-- 
Michael Hicks
Ph.D. Candidate, the University of Pennsylvania
http://www.cis.upenn.edu/~mwh            mailto://mwh@dsl.cis.upenn.edu
*There was a man who entered a local paper's pun contest; He sent in ten
*different puns, in the hope that at least one of the puns would win.  
*Unfortunately, no pun in ten did.



  reply	other threads:[~2001-01-06 22:18 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
2001-01-03 15:51     ` John Max Skaller
2001-01-03 17:50       ` Markus Mottl
2001-01-05  0:30         ` Michael Hicks [this message]
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=200101050030.f050Uas06293@codex.cis.upenn.edu \
    --to=mwh@dsl.cis.upenn.edu \
    --cc=caml-list@inria.fr \
    --cc=mattias.waldau@abc.se \
    --cc=mottl@miss.wu-wien.ac.at \
    --cc=skaller@ozemail.com.au \
    /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).