caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Stéphane Glondu" <steph@glondu.net>
To: ocsigen@sympa.mancoosi.univ-paris-diderot.fr,
	caml-list <caml-list@inria.fr>
Subject: [ANN] Lwt 2.0.0 released
Date: Fri, 16 Oct 2009 00:10:29 +0200	[thread overview]
Message-ID: <4AD79DD5.5090109@glondu.net> (raw)
In-Reply-To: <4AC682F0.9050808@glondu.net>

[-- Attachment #1: Type: text/plain, Size: 2609 bytes --]

Hello,

The Lwt team is pleased to announce the release of Lwt 2.0.0. You can
download it at:

  https://ocsigen.org/lwt/install


This new version brings a lot of new features, including:

 * GLib integration: it is now possible to write cooperative
   application using GTK!

 * Terminal utilities: you can now write cooperative curses oriented
   application!

 * Cooperative readline: write a shell in 5 minutes!

 * A syntax extension to make code using lwt clearer

 * A proof of concept implementation of a new toplevel with line
   editing and completion support

 * New modules, helpers, ...


Here is the complete list of changes from the previous version
(1.1.0):

 * Adding modules:
   - Lwt_stream: lwt-aware version of the Stream module
   - Lwt_gc for using finalise without Lwt_unix.run
   - Lwt_io: a new implementation of buffered channels with more
     features and better handling of concurrent access
   - Lwt_text: implementation of text channels
   - Lwt_process: helpers to spawn processes and communicate with them
   - Lwt_main for abstracting the main loop and allowing replacement
     by a custom main loop
   - Lwt_glib for integration into the glib main event loop
   - Lwt_term for interaction with the terminal
   - Lwt_read_line for interactive user input
   - Lwt_monitor, Lwt_mvar: combined locks for synchronization with
     conditional variables for notification
   - Lwt_throttle for limiting rate of execution (e.g. for
     authentication procedures)
   - Lwt_sequence: mutable sequence of elements
   - Lwt_event, Lwt_signal: helpers for reactive programming with lwt
 * Adding a syntax extension pa_lwt:
   - handles anonymous bind a >> b
   - adds syntactic sugar for catching errors (ticket #6)
   - adds syntactic sugar for parallel let-binding construction
   - adds syntactic sugar for for-like loops
 * Top-level integration:
   - threads can runs while reading user input
   - line editing support
 * New enhanced OCaml toplevel with some basic completion features
 * Adding C stubs to reimplement Unix.read and Unix.write with
   assumption of non-blocking behaviour
 * Adding more functions/helpers in Lwt
 * Fixing memory leaks in Lwt.choose
 * Bugfix in Lwt_chan.close_* (ticket #66)
 * Separate the type of threads (covariant) from the type of thread
   wakeners (contravariant); the type of many functions related to
   Lwt.wait has been changed
 * Add cancelable threads
 * Unix-dependent part is now put in its own archive and findlib
   package.


Enjoy!

-- 
The Lwt team


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 899 bytes --]

           reply	other threads:[~2009-10-15 22:10 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <4AC682F0.9050808@glondu.net>]

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=4AD79DD5.5090109@glondu.net \
    --to=steph@glondu.net \
    --cc=caml-list@inria.fr \
    --cc=ocsigen@sympa.mancoosi.univ-paris-diderot.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;
as well as URLs for NNTP newsgroup(s).