Here is the latest Caml Weekly News, for the week of March 04 to 11, 2008.
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/7deeba320b2017d0/bc36c74f1a7b5480#bc36c74f1a7b5480Hezekiah M. Carty announced:
I wrote a myocamlbuild.ml to use camlidl from within ocamlbuild if anyone is interested. I would also be happy to receive any pointers on how to improve this. The relevant files can be found here: http://code.google.com/p/ocaml-plplot/source/browse/trunk/ The important pieces are: - myocamlbuild.ml which has a "rule" section for handling .idl files - libocaml_plplot.clib which defines the C portion of the library wrapper - Makefile which exports some environment variables and handles a few other items The Makefile could be folded in to myocamlbuild.ml with a few Unix.open_process_in calls, but I don't see a need to do so at this time. Once this has been refined a bit I will add it or ask that it be added to the ocamlbuild wiki.
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/dbf0e442b5deb62c/cf7bc4d352aaf1ab#cf7bc4d352aaf1abJohn Whitington announced:
I've just uploaded a new version of our library for reading and writing PDF files from within Ocaml - CamlPDF. New features: o CCITTFaxDecode support (Group 3 1D and Group 4) o Fully re-entrant o Parsing of Type 3 fonts o Bit-by-bit operations (e.g some decoders) much faster and of course many bugfixes and improvements. Thanks to those who've provided suggestions for this release. For the next release I'm planning on bringing a bunch of high level operations I wrote for our commercial software into the library: suggestions on that requested. http://www.coherentgraphics.co.uk/camlpdf.html
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/1173790aef3a3292/1439e5ad28f8d174#1439e5ad28f8d174Continuing this thread, Xavier Clerc said:
> However, I noticed a bug with the binary package that does not show up if > you have the standard OCaml distribution installed on your computer: the > ocamlc.jar/ocamljava.jar compilers will fail if the current directory > contains the by-product of a previous compilation (e.g. cmo or cmi files). > The temporary workaround is to delete these files before any compilation. > > I suspect this bug has something to do with the embedded mode (the ability > for the Java-run programs to look for files inside their jar files rather > than on the local file system). I will hunt this bug and report to the list > when it is fixed. Sorry for the inconvenience in the meanwhile. This bug, as well as some other ones, have been fixed in the newly updated version. To keep in touch with updates, one can refer to the RSS feed: feed://ocamljava.x9c.fr/rss.xml
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/274ecad2c8e41d43/ab69bd4e3f31fe34#ab69bd4e3f31fe34Richard Jones announced:
http://et.redhat.com/~rjones/ocaml-newt/ Newt is a text mode window library. It's most famous (notorious?) use is in the anaconda installer for Fedora and Red Hat Enterprise Linux. These are OCaml bindings for newt. There are some screenshots of anaconda here so you can get the idea of what newt is all about: http://news.softpedia.com/news/Fedora-Core-6-Text-Mode-Installation-Guide-43302.shtml
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/f3ad69114292e065/7c5336f094616b94#7c5336f094616b94Romain Beauxis announced:
Along with our project (liquidsoap), we (the savonet team) have developped an advanced scheduler that we needed for our software. It is now available as a seperate module, and we hope it could be usefull for some of you. The basics of this scheduler is to implement a wrapper around Unix.select in order to be able to wait for events on a socket and/or a given delay and execute a task when one of the waited events occured. We also wrote an asynchronous interface as well as a simple I/O interface, in order to read and write to sockets, or submit an asychronous task to a scheduler. Several queues can be run against the same scheduler, each one living in a different thread. Also, each task has a priority, which can of your favorite type, and each queue decides if it wants to process a task according to a predicate passed at its initialisation. This scheduler can be very usefull to write simple servers, as well as to develop a multi-thread task processing system. Two simple telnet and http examples are provided in the source. You can find more informations on the module there: http://www.rastageeks.org/duppy.html In particular, the documentation is available there: http://www.rastageeks.org/ocaml-duppy/Duppy.html You can also download the module there: https://sourceforge.net/project/showfiles.php?group_id=89802&package_id=266393Gerd Stolpmann asked and Romain Beauxis answered:
> How is that different from my equeue approach? Well, it is very similar, clearly. The difference I can see for now, is that Duppy is more simple and oriented toward socket events and delays. In particular, it is not clear to me wether equeue can accept delayed tasks. Of course, we didn't meant to deprecate your work, but perhaps it can be usefull for different taks..Later on, Gerd Stolpmann added:
My question was only out of curiosity. I am sometimes interested why people reinvent wheels - and if it is only for a different color. Equeue supports delays. It doesn't support priorities, however. Also, multi-threading integration seems to be different.
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/b0043c2c5714cb1a/f8342697120413fd#f8342697120413fdSylvain Le Gall announced:
During the last three weeks, the OCamlCore.org Team has been working to set up various software services for the OCaml community. Following the previous announcement  of the availability of an OCaml planet (i.e. an aggregation of blogs discussing OCaml-related topics), we are now almost ready to announce an OCaml forge. A forge is a set of services for software projects, including version control systems (CVS, SVN, ...), mailing lists, download areas, bug tracking systems, ... Well known examples are sourceforge.net, GNA, and Savannah. The forge for the OCaml community will be specifically aimed at hosting software projects related to the OCaml programming language. The new site is almost ready for the release. However, before open it to everybody, we would like to gather a group of people from the community to beta-test the site. In particular, we are therefore looking for people which: * have a small experience with other forge have an OCaml project to * start (or to migrate from somewhere else) are willing to collaborate * with us to find out problems in the forge setup Of course, this being a test period, we are not yet willing to give guarantees of any kind, but we do have backups :-) So if you want to participate to the beta test of forge.ocamlcore.org, sign-up for an account on http://forge.ocamlcore.org. Then submit a project, stating into "Objectifs et description du projet" that "Project will belong to the beta test of forge.ocamlcore.org". This is for records and help us to be sure that project submitter is aware of the "beta" status of the forge. For the moment we are *not* going to accept projects which do not explicitly acknowledge the beta testing status of the forge. Regards, the OCamlCore.org Team. (Sylvain Le Gall, Romain Beauxis, Stefano Zacchiroli, Pietro Abate)  http://groups.google.com/group/fa.caml/msg/6faedd72f77fd0df
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/89c4c0992bee6762/555c27e15ba00a74#555c27e15ba00a74Yaron Minsky announced:
I thought people might be interested in the blog that we've just started: http://ocaml.janestcapital.com In addition to our random musings, we plan on posting occasional tutorials focusing on things we've learned over the years about programming effectively in OCaml. Our hope is to make this a useful resource to the community at large. The blog allows for comments, and we're eager to have people join in the discussion.
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/9535b0362d76d909/3684c452a5e12285#3684c452a5e12285Berke Durak announced:
Archive: http://groups.google.com/group/fa.caml/browse_frm/thread/066f9cd339d3c974/d4037122a0b31777#d4037122a0b31777Eijiro Sumii announced:
CALL FOR PAPERS The 2008 ACM SIGPLAN Workshop on ML Sunday, September 21, 2008 Victoria, British Columbia, Canada To be held in conjunction with ICFP 2008 http://www.kb.ecei.tohoku.ac.jp/ml2008/ IMPORTANT DATES: Submission deadline: Monday, June 23, 2008 Notification of acceptance: Friday, July 18, 2008 Final revision due: Monday, July 28, 2008 Workshop: Sunday, September 21, 2008 GOALS OF THE WORKSHOP: ML is a family of programming languages that includes dialects known as Standard ML, Objective Caml, and F#. The development of these languages has inspired a large amount of computer science research, both practical and theoretical. This workshop aims to build on previous occasions (recent instances are ML 2005 in Tallinn, Estonia, 2006 in Portland, Oregon, and 2007 in Freiburg, Germany), providing a forum to encourage discussion and research on ML and related technology. The 2008 Workshop on ML will be held in conjunction with the 13th ACM SIGPLAN International Conference on Functional Programming (ICFP 2008) in Victoria, British Columbia, Canada on Sunday, September 21, 2008. This year we extend the scope of the workshop from ML itself to technologies closely related to ML (higher-order, typed, or strict languages) and invite high-quality papers in all areas of crucial importance for the future of ML. SUBMISSION GUIDELINES: We seek papers on topics related to ML, including (but not limited to): * applications * extensions: objects, classes, concurrency, distribution and mobility, semi-structured data handling, etc. * type systems (static and dynamic): inference, effects, overloading, error reporting, contracts, specifications and assertions, etc. * implementation: compilers, interpreters, partial evaluators, garbage collectors, etc. * environments: libraries, tools, editors, debuggers, cross-language interoperability, functional data structures, etc. * semantics Submitted papers should describe new ideas, experimental results, ML-related projects, or informed positions regarding proposals for next-generation ML languages. In order to encourage lively discussion, submitted papers may describe work in progress. All papers will be judged on a combination of correctness, significance, novelty, clarity, and interest to the community. All paper submissions must be at most 12 pages total length in the standard ACM SIGPLAN two-column conference format (9pt): http://www.acm.org/sigs/sigplan/authorInformation.htm Accepted papers will be published by the ACM and will appear in the ACM Digital Library. More details about the submission procedure will be announced later on the web page: http://www.kb.ecei.tohoku.ac.jp/ml2008/ PROGRAM CHAIR: Eijiro Sumii (Tohoku University) PROGRAM COMMITTEE: Sylvain Conchon (Paris-Sud University / INRIA Saclay-Ile-de-France) Karl Crary (Carnegie Mellon University) Andrzej Filinski (DIKU) Robby Findler (The University of Chicago) Cormac Flanagan (University of California at Santa Cruz) Alain Frisch (LexiFi) Dan Grossman (University of Washington) Didier Remy (INRIA Paris-Rocquencourt) Claudio Russo (Microsoft Research Cambridge) Eijiro Sumii (Tohoku University) Hongwei Xi (Boston University)
Here is a quick trick to help you read this CWN if you are viewing it using vim (version 6 or greater).
If you know of a better way, please let me know.
If you happen to miss a CWN, you can send me a message and I'll mail it to you, or go take a look at the archive or the RSS feed of the archives.
If you also wish to receive it every week by mail, you may subscribe online.