From: Jon Harrop <jon@jdh30.plus.com>
To: caml-list@yquem.inria.fr
Subject: Re: [Caml-list] MinCaml: an educational compiler for tiny ML subset (documented in Japanese)
Date: Mon, 7 Mar 2005 00:20:53 +0000 [thread overview]
Message-ID: <200503070020.53784.jon@jdh30.plus.com> (raw)
In-Reply-To: <20050305.093742.46637291.eijiro_sumii@anet.ne.jp>
On Saturday 05 March 2005 14:37, Eijiro Sumii wrote:
> From: "Jon Harrop" <jon@jdh30.plus.com>
> > Did you choose SPARC because of availability or for technical reasons?
>
> Both - Sun is still strong in universities around me and IA-32 is a
> mess (for me, at least) compared to RISC...
Yes indeed! :-)
Are you interested in commercialising this project? I think that many
companies would be interested in a mini compiler which they could customise
themselves, e.g. to create JIT compilers, or to have a decent embedded
language.
Obviously this would require more work but I do not believe it would take
someone (suitably talented, such as yourself) very long.
> > What features of ML are implemented?
>
> Only a _very_ tiny subset: for now, it does not have polymorphism,
> data types, modules, nor garbage collection (so I shouldn't even call
> it ML, except that the syntax is a subset of OCaml). However, it
> _does_ have type inference,
I'd prioritise data types next, and pattern matching (of course) if that is
not implemented already.
> higher-order functions, floating-point
> numbers, tuples, and arrays with destructive update - which are
> sufficient for minimal examples (such as gcd, ack, matrix, etc.) and
> one application (raytracing).
Amazing!
> The subset is so tiny because MinCaml was developed for an
> undergraduate course, where I put most energy to the ease of
> understanding and couldn't include many features. However, adding
> them would be a nice project for more advanced students.
Might I suggest an OCaml byte-code back end? Then you could "borrow" the OCaml
GC.
> By the way, for the majority of people who do not speak Japanese:-), I
> am preparing an Enlish documentation.
Marvellous, thank you. :-)
--
Dr Jon D Harrop, Flying Frog Consultancy Ltd.
Objective CAML for Scientists
http://www.ffconsultancy.com/products/ocaml_for_scientists
next prev parent reply other threads:[~2005-03-07 0:19 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 22:26 Eijiro Sumii
2005-03-05 8:32 ` [Caml-list] " Jon Harrop
2005-03-05 14:37 ` Eijiro Sumii
2005-03-05 14:48 ` Eijiro Sumii
2005-03-07 0:20 ` Jon Harrop [this message]
2005-03-08 3:01 ` MinCaml English Documentation Eijiro Sumii
2005-03-08 4:12 ` Jon Harrop
2005-03-08 7:09 ` [Caml-list] " Ken Friis Larsen
2005-03-08 18:59 ` David MENTRE
2005-03-08 19:15 ` Eijiro Sumii
2005-03-08 20:13 ` Xavier Leroy
2005-03-08 22:32 ` Eijiro Sumii
2005-03-14 17:31 ` Looking for an efficient implementation of simply typed lambda calculus Sébastien Hinderer
2005-03-15 20:59 ` [Caml-list] " Manos Renieris
2005-03-05 9:46 ` [Caml-list] MinCaml: an educational compiler for tiny ML subset (documented in Japanese) Corey O'Connor
2005-03-05 12:01 ` Oliver Bandel
2005-03-05 16:45 ` Eijiro Sumii
2005-03-05 17:19 ` OT: " Richard 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=200503070020.53784.jon@jdh30.plus.com \
--to=jon@jdh30.plus.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