caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "forum@x9c.fr" <forum@x9c.fr>
To: caml users <caml-list@inria.fr>
Cc: Xavier Clerc <forum@x9c.fr>
Subject: Re: [Caml-list] A js_of_ocaml equivalent for the JVM?
Date: Fri, 9 Mar 2012 19:05:25 +0100	[thread overview]
Message-ID: <051FF700-7AB2-43CE-A917-53461BB3EEE6@x9c.fr> (raw)
In-Reply-To: <4F5A41C6.10505@inria.fr>


Le 9 mars 2012 à 18:45, Johan Grande a écrit :

> Le 09/03/2012 18:12, Philippe Veber a écrit :
>> Dear camlers,
>> I used js_of_ocaml several times and was really stunned of how clever
>> (notably because writing interfaces boils down to writing types) and
>> efficient this approach is. Would a similar thing work for the JVM, that
>> is a compiler from ocaml bytecode to java bytecode?

It is not easy to envision such a tool on the JVM, because of the current
restrictions imposed on Java bytecode. As an example, the size of a method
is currently limited to 64Ko, which is clearly way too small for non trivial
programs.


>> I guess it wouldn't
>> provide a full interoperability with java, in the sense that creating or
>> extending classes may not be possible (well, why not after all?).
>> However, being able to run an ocaml program on the JVM reusing existing
>> java libraries would be so useful already!

I am currently working on this for OCaml-Java (see below).


>> Are there known obstacles to this? Has anyone tried something in this
>> direction?

Well, no real obstacle as OCaml-Java showed.
However, OCaml-Java 1.x is still a bare proof of concept due to both
poor design choices and JVM limitations. But then came Java 1.7 and
some limitations were removed (e. g. a garbage collector better suited
to functional languages, and an implementation of method handles).
OCaml-Java has been largely rewritten and now exhibit acceptable
performances.


>> Would there be a chance to support multicore programming that
>> way?

Yes, it is actually working. But not released yet.
Starting from vanilla OCaml, you "only" need two things:
  1/ have a reentrant runtime;
  2/ have a parallel garbage collector.
OCaml-Java implements the former, while all modern JVMs provide the latter.
So, basically, it just works. The great difficulty is then to provide the good
abstractions to make the life of the programmer as easy as possible.
I mean: who would like to program with locks?


>> I hope these are not silly questions (sorry if they are!)
> 
> http://ocamljava.x9c.fr

Thanks for the plug. However, OCaml-Java is quite different and provides two tools:
  - an equivalent of ocamlrun written in Java (meaning you can interpret
    OCaml bytecode inside a JVM);
  - an equivalent of ocamlc/ocamlopt for Java (meaning you can compile
    OCaml sources to Java jar files to be executed by a JVM).


Kind regards,

Xavier Clerc



  reply	other threads:[~2012-03-09 18:05 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-09 17:12 Philippe Veber
2012-03-09 17:45 ` Johan Grande
2012-03-09 18:05   ` forum [this message]
2012-03-12 16:05     ` Philippe Veber
2012-03-13 16:55     ` Richard W.M. Jones

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=051FF700-7AB2-43CE-A917-53461BB3EEE6@x9c.fr \
    --to=forum@x9c.fr \
    --cc=caml-list@inria.fr \
    /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).