From: Jeremy Bem <jeremy1@gmail.com>
To: caml-list List <caml-list@yquem.inria.fr>
Subject: interest in a much simpler, but modern, Caml?
Date: Fri, 6 Aug 2010 00:04:34 -0400 [thread overview]
Message-ID: <AANLkTi=UuefVu9CmwwomimGzMqFrks5SZ+227Znv5r+z@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1699 bytes --]
Dear caml-list,
To support my research, I've developed an implementation ("Llama Light") of
the core Caml language. Modules, objects, labels etc are not supported
(except for file-level modules). The system strongly resembles OCaml,
however the completely rewritten typechecker is not only much smaller in
terms of lines-of-code; it has a genuinely simpler design owing especially
to the lack of first-class modules. This wasn't obtained by stripping down
OCaml, but rather by integrating OCaml features into Caml Light (although
this history isn't visible in the end result). In a strict type-theoretic
sense, the system is even simpler than Caml Light; I'll postpone the
details.
The system is fully self-hosting; all the main tools have been ported to the
smaller language, e.g. "llamadoc" replaces ocamldoc, etc. The standard
library has been ported as well, such as non-functorial versions of the Map
and Set modules. Only the native-code compiler is missing, and that doesn't
look like more than a day's work or so.
My plans now call for adding features to replace the ones I've removed,
namely experimental ones related to assisted theorem proving and inductive
programming. However, it occurs to me that others might find the
stripped-down "base system" to be useful for their own experiments.
Obtaining it was a non-trivial amount of work, and I've tried to write the
code clearly and carefully. So -- this posting is intended as a gauge of
interest. How much effort should I expend to package what I've got, before
adding my own experimental features? With community support (and a good
approach to the Q License), maybe I could manage something fairly polished.
Thanks,
Jeremy
[-- Attachment #2: Type: text/html, Size: 1882 bytes --]
next reply other threads:[~2010-08-06 4:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-06 4:04 Jeremy Bem [this message]
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='AANLkTi=UuefVu9CmwwomimGzMqFrks5SZ+227Znv5r+z@mail.gmail.com' \
--to=jeremy1@gmail.com \
--cc=caml-list@yquem.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