From: "Stéphane Glondu" <steph@glondu.net>
To: caml-list <caml-list@inria.fr>,
ocsigen@sympa.mancoosi.univ-paris-diderot.fr
Subject: [ANN] Lwt 2.1.0 released
Date: Mon, 19 Apr 2010 21:03:31 +0200 [thread overview]
Message-ID: <4BCCA903.1070307@glondu.net> (raw)
Hello,
The Lwt team is pleased to announce the release of Lwt 2.1.0. You can
download it at:
http://ocsigen.org/lwt/install
Here is a list of changes from the previous version (2.0.0):
* Rename Lwt.select to Lwt.pick
* Removing module Lwt_monitor in favour of Lwt_mutex and
new module Lwt_condition
* More react helpers:
- Lwt_event.next
- Lwt_event.limit and Lwt_signal.limit
- Lwt_event.from
* Adding function Lwt_main.fast_yield
* Adding unit tests
* Optimisation of Lwt
* Adding module Lwt_log for logging
* Adding a camlp4 filter for remmoving logging statement or inlining
tests
* Adding module Lwt_daemon
* Adding function Lwt_unix.recv_msg and Lwt_unix.send_msg
* Adding function Lwt_unix.wait4
* Adding function Lwt_io.establish_server
* Adding module Lwt_list
* Enhancement in Lwt_process, it now support redirections and
timeouts
* Allow to use select on arbitrary high file descriptors
* More commands and features in Lwt_read_line:
- Handle "undo" command
- New controlable read-lines instances
- More edition commands
- Completion as you type
- Backward search
* Enhancement in Lwt_term: more drawing functions and allow to
put the terminal into drawing mode
* Optimisation of Lwt_stream
* Optimisation of Lwt_io.write_char and Lwt_io.read_char
* Bugfix of Lwt_stream: two parallel Lwt_stream.get
returned the same value
* Bugfix in Lwt_unix.connect: it returned immediatly on EINPROGRESS
* Bugfixes in Lwt_glib: file descriptors were not monitored correctly
Enjoy!
--
Stéphane Glondu, on behalf of the Lwt team
reply other threads:[~2010-04-19 19:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=4BCCA903.1070307@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).