Sunday, November 13, 2011
Hi, I’m going to work through http://www.ccs.neu.edu/home/matthias/BTML/ and http://www.cl.cam.ac.uk/~lp15/MLbook/ using http://www.smlnj.org/ SLOWLY over MANY MONTHS. The reason is that I’ve never learned a statically typed functional programming language, I feel weak on recursive data type definitions, and I am curious about compiler and interpreter construction. So, I’m looking for a way to learn about all [...]
This project brings Objective Caml into the set of tools which allow to program PIC microcontrollers. (via Anil)
Saturday, November 6, 2010
Here is an old post comparing Stalin Scheme to OCaml, among a few other languages. Here is the article on Jon’s page. Stalin seems pretty amazing.
Friday, September 24, 2010
The Enhanced Ocaml Documentation is provided by Hendrik Tews; basically it visually highlights any difference between the previous and current version of the documentation. Here is how he does it: I diff the txt versions of the reference manual and change the html version by hand. For the grammar rule index I use a tool [...]
Friday, September 24, 2010
For an accessible introduction to modern (>= 3.10) Camlp4, you may be interested in Jake Donham’s blog post series “Reading Camlp4″ : http://ambassadortothecomputers.blogspot.com/search/label/camlp4 You will also find valuable (though incomplete) information on the camlp4 wiki : http://brion.inria.fr/gallium/index.php/Camlp4 The older version of camlp4 (< 3.10, now called camlp5) also provides a documentation http://caml.inria.fr/pub/docs/tutorial-camlp4/index.html , and you [...]
Monday, September 13, 2010
Efforts being made on one of the biggest criticisms of OCaml. (via Caml-list)
Saturday, September 11, 2010
Here is how to get Unison running on the iPhone. Nice. Via Sylvain via LinkedIn-Ocaml Developers.
Wednesday, September 1, 2010
I’m very proud to announce Ocamlnet 3.0.0, a completely overhauled version of Ocamlnet. Wish I had some problems that needed solving with ocamlnet! (via caml-list)
* Favor readers over writers * Create uniform interfaces * Make illegal states unrepresentable * Code for exhaustiveness * Open few modules * Make common errors obvious * Avoid boilerplate * Avoid complex type-hackery * Don’t be puritanical about purity (via janestreet)