Mailing list for all users of the OCaml language and system.
 help / color / mirror / Atom feed
From: Jon Harrop <jonathandeanharrop@googlemail.com>
To: "'ivan chollet'" <ivan.chollet@gmail.com>, <caml-list@yquem.inria.fr>
Cc: <jeremy1@gmail.com>
Subject: RE: [Caml-list] interest in a much simpler, but modern, Caml?
Date: Wed, 11 Aug 2010 14:19:06 +0100	[thread overview]
Message-ID: <03fc01cb3957$c79e2800$56da7800$@com> (raw)
In-Reply-To: <AANLkTimM1GSMK2W5xEJFdZkZezB7V03+qJDkHAA+sK79@mail.gmail.com>

Ivan wrote:
> I have noted that there are now many implementation of OCaml. Namely :
> - caml light
> - jocaml
> - mincaml
> - your implementation ?
> etc.
>
> which means there is a lot of interest in implementing tools and runtimes
for ML. 

I'm not sure 3.5 implementations over 25 years is a "lot" of interest but
maybe if you add HLVM... ;-)

> Well, now I'm thinking that the community should start a project like
Parrot (with JIT optionally)
> but dedicated to ML.

I already did something like this called HLVM:

  http://www.ffconsultancy.com/ocaml/hlvm/

> The existing ocaml runtime is amazing but it's definitely not very
community friendly and is in my
> opinion a bit hard to understand given the scarcity of design documents.

Feel free to ask me anything about HLVM's design. We have a dedicated
mailing list:

  https://lists.forge.ocamlcore.org/pipermail/hlvm-list/

> A real community project with real documentation might be interesting for
teaching purposes but also
> in production environments.

HLVM might be interesting for teaching purposes because it is tiny (2kLOC)
and comprehensible whilst providing advanced features like JIT compilation
(for a native-code REPL!) and a multicore-capable garbage collector (in only
100LOC!). HLVM should also be suitable for production environments.

I had actually forgotten about the mincaml project but mincaml's front-end
with HLVM's back-end sounds like a match made in heaven...

Cheers,
Jon.



  parent reply	other threads:[~2010-08-11 13:19 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09  6:37 ivan chollet
2010-08-09 10:54 ` Cedric Cellier
2010-08-09 15:00 ` ivan chollet
2010-08-09 15:03 ` ivan chollet
2010-08-11 13:19 ` Jon Harrop [this message]
2010-08-11 16:12   ` philippe
2010-08-12  6:56   ` ivan chollet
  -- strict thread matches above, loose matches on Subject: below --
2010-08-06  4:04 Jeremy Bem
2010-08-06 13:50 ` [Caml-list] " Eray Ozkural
2010-08-08 17:59 ` Florian Weimer
2010-08-08 18:44   ` Jeremy Bem
2010-08-08 18:52     ` Florian Weimer
2010-08-08 19:39       ` Jeremy Bem
2010-08-09 11:55         ` Nicolas Pouillard
2010-08-11 13:00         ` Jon Harrop
2010-08-08 20:53       ` Nicolas Pouillard
2010-08-08 20:59         ` Jeremy Bem
2010-08-08 21:47           ` bluestorm
2010-08-08 23:00             ` Christophe TROESTLER
2010-08-08 23:29             ` Jeremy Bem
2010-08-11 13:02               ` Jon Harrop
2010-08-12  0:21                 ` Jeremy Bem
2010-08-12 23:14                   ` Jon Harrop
2010-08-09 13:10             ` David House
2010-08-09 14:03               ` Nicolas Pouillard
2010-08-08 20:52     ` Nicolas Pouillard
2010-08-11 12:56     ` Jon Harrop

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='03fc01cb3957$c79e2800$56da7800$@com' \
    --to=jonathandeanharrop@googlemail.com \
    --cc=caml-list@yquem.inria.fr \
    --cc=ivan.chollet@gmail.com \
    --cc=jeremy1@gmail.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