<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>Hello,</div><div><br></div><div>Here is the latest Caml Weekly News, for the week of June 02 to 09, 2009.</div><div><br></div><div>1) OCaml/Sqlite ORM layer (preview 0.2)</div><div>2) Probabilistic programming in OCaml</div><div>3) OCaml 3.11.1+rc1</div><div>4) ML 2009 Call for Demos</div><div>5) Which types for representing HTML documents ?</div><div>6) Other Caml News</div><div><br></div><div>========================================================================</div><div>1) OCaml/Sqlite ORM layer (preview 0.2)</div><div>Archive: <<a href="http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/80eefd151c3c40db637f72b25fcac36a.en.html">http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/80eefd151c3c40db637f72b25fcac36a.en.html</a>></div><div>------------------------------------------------------------------------</div><div>** Anil Madhavapeddy announced:</div><div><br></div><div>I've been using OCaml in a few server projects which need a light- </div><div>weight database, and so I wrote a library to map OCaml objects </div><div>directly to a SQLite3 backend database.</div><div><br></div><div>Like other ORM systems, you define a schema based on sets of named </div><div>fields. The Sql_orm library then generates an OCaml module and </div><div>interface with static accessor methods which take care of all the </div><div>tedious SQL interactions and provide you with a nice high-level, </div><div>statically type-safe access method.</div><div><br></div><div>It's still early days but the library is very functional and stable. </div><div>I've put up docs and instructions at:</div><div><<a href="http://wiki.github.com/avsm/ocaml-orm-sqlite">http://wiki.github.com/avsm/ocaml-orm-sqlite</a>></div><div><br></div><div>It's currently written as a module which outputs OCaml directly, and </div><div>once I'm happy with the feature-set, I intend to port it to use camlp4 </div><div>so that schemas can be declared directly without the need to </div><div>regenerate a separate ML file.</div><div><br></div><div>You can view an example schema at: <<a href="http://tinyurl.com/sqlorm-example">http://tinyurl.com/sqlorm-example</a>></div><div>- schema.ml declares the fields</div><div>- test.ml uses it</div><div>- my_db.* are the generated files.</div><div>- the tests/ directory has more advanced usage, such as foreign keys </div><div>and so on.</div><div> </div><div>========================================================================</div><div>2) Probabilistic programming in OCaml</div><div>Archive: <<a href="http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/fbd251353f71c81388f0a07febb5455e.en.html">http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/fbd251353f71c81388f0a07febb5455e.en.html</a>></div><div>------------------------------------------------------------------------</div><div>** Continuing the thread from last week, Eliot Handelman asked and Oleg replied:</div><div><br></div><div>> This looks really interesting,. but can it be compiled with 3.10.1?</div><div>> First bash at compiling the delimcc library failed.</div><div><br></div><div>Yes, the library can be used with 3.10.1 and even 3.09. I think I know</div><div>what problem you have encountered. Ideally, to compile delimcc you</div><div>need the configured OCaml sources, because delimcc needs a few header</div><div>files that are not normally installed. Since one could install OCaml</div><div>from a binary distribution, the sources are not necessarily</div><div>available. Therefore, delimcc includes the needed header files as part</div><div>of its distribution, for the most common platform: ia32 and</div><div>Linux/BSD. Alas, these files differ slightly among OCaml versions</div><div>(e.g., because of renaming). Therefore, delimcc distribution includes</div><div>two sets of files, in the directories ocaml-byterun-3.09 and</div><div>ocaml-byterun-3.10. With OCaml 3.10.1, one has to use</div><div>ocaml-byterun-3.09 files rather than ocaml-byterun-3.10. Sorry, this</div><div>is indeed confusing.</div><div><br></div><div>Thus, you may want to edit the Makefile in delimcc, comment out the</div><div>line</div><div><span class="Apple-tab-span" style="white-space:pre"> </span>OCAMLINCLUDES=./ocaml-byterun-3.10</div><div>and uncomment the line above that contains 3.09. I think it would</div><div>build delimcc library (please `make testd0' to make sure).</div><div> </div><div>========================================================================</div><div>3) OCaml 3.11.1+rc1</div><div>Archive: <<a href="http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/77ab6ab4f73547157f7100339ab19302.en.html">http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/77ab6ab4f73547157f7100339ab19302.en.html</a>></div><div>------------------------------------------------------------------------</div><div>** Damien Doligez announced:</div><div><br></div><div>We fixed a few bugs from OCaml 3.11.1+rc0, and prepared a new release </div><div>candidate.</div><div>The main changes from rc0 are the following.</div><div><br></div><div>- PR#4796: ocamlyacc: missing NUL termination of string</div><div>- PR#4798: compilation of ocamldoc.opt fails under windows</div><div>- PR#4804: bug in Big_int.int64_of_big_int on 32-bit platforms.</div><div>- PR#4805: improving compatibility with the clang C compiler</div><div>- PR#4809: issue with Unix.create_process under Win32</div><div><br></div><div>The changes from 3.11.0 are listed at the end of this mail.</div><div><br></div><div><br></div><div>If you haven't tested rc0, or if you had a problem with one of the above</div><div>bugs, please test rc1 now and send me some feedback. This release</div><div>candidate is available in source code at</div><div><<a href="ftp://ftp.inria.fr/INRIA/cristal/ocaml/ocaml-3.11/ocaml-3.11.1+rc1.tar.gz">ftp://ftp.inria.fr/INRIA/cristal/ocaml/ocaml-3.11/ocaml-3.11.1+rc1.tar.gz</a>></div><div><br></div><div>We seem to have a small problem remaining in build/install.sh. It </div><div>will be</div><div>fixed for the release.</div><div><br></div><div>Happy hacking,</div><div><br></div><div>-- Damien for the OCaml team</div><div><br></div><div><br></div><div>Objective Caml 3.11.1:</div><div>----------------------</div><div><br></div><div>Bug fixes:</div><div>- PR#4095: ocamldebug: strange behaviour of control-C</div><div>- PR#4403: ocamldebug: improved handling of packed modules</div><div>- PR#4650: Str.regexp_case_fold mis-handling complemented character </div><div>sets [^a]</div><div>- PR#4660: Scanf.format_from_string: handling of double quote</div><div>- PR#4666: Unix.exec* failure in multithread programs under MacOS X </div><div>and FreeBSD</div><div>- PR#4667: debugger out of sync with dynlink changes</div><div>- PR#4678: random "out of memory" error with systhreads</div><div>- PR#4690: issue with dynamic loading under MacOS 10.5</div><div>- PR#4692: wrong error message with options -i and -pack passed to </div><div>ocamlc</div><div>- PR#4699: in otherlibs/dbm, fixed construction of dlldbm.so.</div><div>- PR#4704: error in caml_modify_generational_global_root()</div><div>- PR#4708: (ocamldoc) improved printing of infix identifiers such as </div><div>"lor".</div><div>- PR#4722: typo in configure script</div><div>- PR#4729: documented the fact that PF_INET6 is not available on all </div><div>platforms</div><div>- PR#4730: incorrect typing involving abbreviation "type 'a t = 'a"</div><div>- PR#4731: incorrect quoting of arguments passed to the assembler on </div><div>x86-64</div><div>- PR#4735: Unix.LargeFile.fstat cannot report size over 32bits on Win32</div><div>- PR#4740: guard against possible processor error in</div><div> {Int32,Int64,Nativeint}.{div,rem}</div><div>- PR#4745: type inference wrongly produced non-generalizable type </div><div>variables.</div><div>- PR#4749: better pipe size for win32unix</div><div>- PR#4756: printf: no error reported for wrong format '%_s'</div><div>- PR#4758: scanf: handling of \<newline> by format '%S'</div><div>- PR#4766: incorrect simplification of some type abbreviations.</div><div>- PR#4768: printf: %F does not respect width and precision </div><div>specifications</div><div>- PR#4769: Format.bprintf fails to flush</div><div>- PR#4775: fatal error Ctype.Unify during module type-checking </div><div>(temporary fix)</div><div>- PR#4776: bad interaction between exceptions and classes</div><div>- PR#4780: labltk build problem under Windows.</div><div>- PR#4790: under Windows, map ERROR_NO_DATA Win32 error to EPIPE Unix </div><div>error.</div><div>- PR#4792: bug in Big_int.big_int_of_int64 on 32-bit platforms.</div><div>- PR#4796: ocamlyacc: missing NUL termination of string</div><div>- PR#4804: bug in Big_int.int64_of_big_int on 32-bit platforms.</div><div>- PR#4805: improving compatibility with the clang C compiler</div><div>- PR#4809: issue with Unix.create_process under Win32</div><div>- Module Parsing: improved computation of locations when an ocamlyacc </div><div>rule</div><div> starts with an empty nonterminal</div><div>- Type-checker: fixed wrong variance computation for private types</div><div>- x86-32 code generator, MSVC port: wrong "fld" instruction generated.</div><div>- ocamlbuild: incorrectly using the compile-time value of $OCAMLLIB</div><div>- Makefile problem when configured with -no-shared-libs</div><div>- ocamldoc: use dynamic loading in native code</div><div><br></div><div>Other changes:</div><div>- Improved wording of various error messages</div><div> (contributed by Jonathan Davies, Citrix).</div><div>- Support for 64-bit mode in Solaris/x86 (PR#4670).</div><div> </div><div>** Richard Jones then said:</div><div><br></div><div>I built this for Fedora:</div><div><br></div><div> <<a href="http://koji.fedoraproject.org/koji/taskinfo?taskID=1392144">http://koji.fedoraproject.org/koji/taskinfo?taskID=1392144</a>></div><div><br></div><div>Not really tested it very much beyond running a few scripts in the</div><div>toplevel.</div><div> </div><div>========================================================================</div><div>4) ML 2009 Call for Demos</div><div>Archive: <<a href="http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/e13782ebab438145bbdba2c76ddf93fa.en.html">http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/e13782ebab438145bbdba2c76ddf93fa.en.html</a>></div><div>------------------------------------------------------------------------</div><div>** Andreas Rossberg announced:</div><div><br></div><div> CALL FOR DEMOS</div><div><br></div><div> 2009 ACM SIGPLAN Workshop on ML</div><div><br></div><div> To be held in conjunction with ICFP 2009</div><div> on Sunday, August 30, 2009</div><div> in Edinburgh, Scotland, UK</div><div><br></div><div> <<a href="http://www.mpi-sws.org/~rossberg/ml2009/">http://www.mpi-sws.org/~rossberg/ml2009/</a>></div><div><br></div><div><br></div><div>Have you written a fancy tool or library that may ease the life of</div><div>fellow ML programmers? Have you developed interesting software using</div><div>your favorite dialect of ML? Or have been producing some cool ML code</div><div>lately that you just want to show off in action?</div><div><br></div><div>Now is your chance to demonstrate it to the world. This year's ML</div><div>Workshop will feature a session for presenting running code written</div><div>in ML, or written for ML. We seek 10-15 minute live demos or tutorials</div><div>related to ML technology that show new developments, interesting</div><div>prototypes, or work in progress.</div><div><br></div><div>The 2009 Workshop on ML will be held in conjunction with the 14th ACM</div><div>SIGPLAN International Conference on Functional Programming (ICFP 2009)</div><div>in Edinburgh, Scotland, UK.</div><div><br></div><div><br></div><div>IMPORTANT DATES</div><div><br></div><div>Demo Submission: Sunday, June 28, 2009</div><div>Notification: Friday, July 10, 2009</div><div>Workshop: Sunday, August 30, 2009</div><div><br></div><div><br></div><div>SUBMISSION GUIDELINES</div><div><br></div><div>Please submit an abstract, about half a page long, describing the demo</div><div>and its technical content. Be sure to include the demo's title, authors,</div><div>collaborators, references and acknowledgements. If you have a project</div><div>website we encourage you to also provide a link that we can put up on</div><div>the ML Workshop home page once your demo is accepted.</div><div><br></div><div>Your demonstration should take 10-15 minutes. The exact length per demo</div><div>will be decided based on the number of accepted submissions. Please notice</div><div>that you will have to bring all hardware and software required for your</div><div>demo yourself -- all the workshop organizers can provide is a projector.</div><div><br></div><div>Please send submissions (in PDF format) with your complete contact</div><div>information via email to <a href="mailto:ml2009@easychair.org">ml2009@easychair.org</a> by June 28, 2009. Please</div><div>feel free to also contact this address if you have further questions.</div><div><br></div><div><br></div><div>PROGRAM CHAIR</div><div><br></div><div>Andreas Rossberg (Max Planck Institute for Software Systems)</div><div><br></div><div>PROGRAM COMMITTEE</div><div><br></div><div>Umut Acar (Toyota Technological Institute at Chicago)</div><div>Damien Doligez (INRIA Paris-Rocquencourt)</div><div>Neal Glew (Intel)</div><div>Andrew Gordon (Microsoft Research Cambridge)</div><div>Patricia Johann (University of Strathclyde)</div><div>Oleg Kiselyov (FNMOC)</div><div>Neelakantan Krishnaswami (Carnegie Mellon University)</div><div>David MacQueen (University of Chicago)</div><div>Yasuhiko Minamide (University of Tsukuba)</div><div>Norman Ramsey (Tufts University)</div><div><br></div><div>STEERING COMMITTEE</div><div><br></div><div>See the ML Workshop series home page at:</div><div><<a href="http://www.tti-c.org/blume/ml-workshop/">http://www.tti-c.org/blume/ml-workshop/</a>></div><div> </div><div>========================================================================</div><div>5) Which types for representing HTML documents ?</div><div>Archive: <<a href="http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/7e6781f7e8c895ace3ca88af5f4c1b16.en.html">http://caml.inria.fr/pub/ml-archives/caml-list/2009/06/7e6781f7e8c895ace3ca88af5f4c1b16.en.html</a>></div><div>------------------------------------------------------------------------</div><div>** Sébastien Hinderer asked and Gabriel Kerneis replied:</div><div><br></div><div>> According to you, how could an HTML document best be represented in</div><div>> OCaml ?</div><div><br></div><div><<a href="http://ocsigen.org/docu/1.2.0/XHTML.M.html">http://ocsigen.org/docu/1.2.0/XHTML.M.html</a>></div><div><br></div><div>The whole website is worth reading if you're interested in web</div><div>programing using Ocaml.</div><div> </div><div>** Richard Jones also replied:</div><div><br></div><div>CDuce is worth considering:</div><div><br></div><div><<a href="http://www.cduce.org/examples.html">http://www.cduce.org/examples.html</a>></div><div> </div><div>** Martin Jambon also replied:</div><div><br></div><div>Ocamlnet's Nethtml works fine for parsing:</div><div><br></div><div>type document =</div><div> Element of</div><div> (string * (string * string) list *</div><div> Nethtml.document list)</div><div> | Data of string</div><div><br></div><div><br></div><div>If your goal is to interpret arbitrary web pages, you have to allow all kinds</div><div>of standard or non-standard elements and attributes anywhere in the document.</div><div><br></div><div>If you are creating HTML documents, beware that you can't embed Flash objects</div><div>using standard HTML. I'm not even speaking of javascript happily manipulating</div><div>the DOM tree with little restrictions.</div><div><br></div><div><br></div><div>Personally I use text templates and validate web pages once they are in my</div><div>browser (using the shortcut to validator.w3.org that opera provides). For</div><div>javascript-generated nodes, I just check that it works in various browsers</div><div>(the firefox "View source chart" extension is useful for debugging the DOM tree).</div><div><br></div><div><br></div><div>I do not suffer at all from the absence of static type-checking of the HTML</div><div>tree. I imagine that the reasons for this are:</div><div><br></div><div>* HTML is the final product and is trivial to debug (no need to printf</div><div>everything since everything is already printed...)</div><div><br></div><div>* There are no complicated conditionals that would leave certain parts of the</div><div>code untested for a long time.</div><div><br></div><div>* Mainstream web browsers are very tolerant. Small accidental deviations from</div><div>the strict W3C standards usually have no visible effect.</div><div> </div><div>========================================================================</div><div>6) Other Caml News</div><div>------------------------------------------------------------------------</div><div>** From the ocamlcore planet blog:</div><div><br></div><div>Thanks to Alp Mestan, we now include in the Caml Weekly News the links to the</div><div>recent posts from the ocamlcore planet blog at <<a href="http://planet.ocamlcore.org/">http://planet.ocamlcore.org/</a>>.</div><div><br></div><div>DJ mix using liquidsoap:</div><div> <<a href="http://blog.rastageeks.org/spip.php?article35">http://blog.rastageeks.org/spip.php?article35</a>></div><div><br></div><div>ocsforge:</div><div> <<a href="http://forge.ocamlcore.org/projects/ocsforge/">http://forge.ocamlcore.org/projects/ocsforge/</a>></div><div><br></div><div>Mise en boîte:</div><div> <<a href="http://misterpingouin.blogspot.com/2009/06/mise-en-boite.html">http://misterpingouin.blogspot.com/2009/06/mise-en-boite.html</a>></div><div><br></div><div>Euler's Power Riffs:</div><div> <<a href="http://alaska-kamtchatka.blogspot.com/2009/06/eulers-power-riffs.html">http://alaska-kamtchatka.blogspot.com/2009/06/eulers-power-riffs.html</a>></div><div><br></div><div>Immutability Redux:</div><div> <<a href="http://alaska-kamtchatka.blogspot.com/2009/06/immutability-redux.html">http://alaska-kamtchatka.blogspot.com/2009/06/immutability-redux.html</a>></div><div><br></div><div>Jim Henson Co.:</div><div> <<a href="http://www.mega-nerd.com/erikd/Blog/CodeHacking/libsndfile/henson.html">http://www.mega-nerd.com/erikd/Blog/CodeHacking/libsndfile/henson.html</a>></div><div><br></div><div>Archimedes:</div><div> <<a href="http://forge.ocamlcore.org/projects/archimedes/">http://forge.ocamlcore.org/projects/archimedes/</a>></div><div><br></div><div>Another Quick Shot of the Desktop Product:</div><div> <<a href="http://coherentpdf.com/blog/?p=36">http://coherentpdf.com/blog/?p=36</a>></div><div><br></div><div>ocaml-orm-sqlite 0.2:</div><div> <<a href="http://caml.inria.fr/cgi-bin/hump.cgi?contrib=701">http://caml.inria.fr/cgi-bin/hump.cgi?contrib=701</a>></div><div><br></div><div>The Battle For Your Address Book:</div><div> <<a href="http://feedproxy.google.com/~r/Skydeck/~3/q61PxbixZ2I/the-battle-for-your-address-book">http://feedproxy.google.com/~r/Skydeck/~3/q61PxbixZ2I/the-battle-for-your-address-book</a>></div><div><span class="Apple-tab-span" style="white-space:pre"> </span></div><div>========================================================================</div><div>Old cwn</div><div>------------------------------------------------------------------------</div><div><br></div><div>If you happen to miss a CWN, you can send me a message</div><div>(<a href="mailto:alan.schmitt@polytechnique.org">alan.schmitt@polytechnique.org</a>) and I'll mail it to you, or go take a look at</div><div>the archive (<<a href="http://alan.petitepomme.net/cwn/">http://alan.petitepomme.net/cwn/</a>>) or the RSS feed of the</div><div>archives (<<a href="http://alan.petitepomme.net/cwn/cwn.rss">http://alan.petitepomme.net/cwn/cwn.rss</a>>). If you also wish</div><div>to receive it every week by mail, you may subscribe online at</div><div><<a href="http://lists.idyll.org/listinfo/caml-news-weekly/">http://lists.idyll.org/listinfo/caml-news-weekly/</a>> .</div><div><br></div><div>========================================================================</div><div class="AppleMailSignature" id="E12A09DE-ADCF-40D6-B7D4-306ED5CADD30"> <div><br class="khtml-block-placeholder"></div><div>-- </div><div>Alan Schmitt <<a href="http://alan.petitepomme.net/">http://alan.petitepomme.net/</a>></div><div><br class="khtml-block-placeholder"></div><div>The hacker: someone who figured things out and made something cool happen.</div><div> .O.</div><div> ..O</div><div> OOO</div><br class="Apple-interchange-newline"> </div><br></body></html>