From: "Jérémie Dimino" <jeremie@dimino.org>
To: caml-list <caml-list@inria.fr>,
ocsigen@sympa.mancoosi.univ-paris-diderot.fr
Subject: [Caml-list] [ANN] Lwt 2.4.0
Date: Mon, 23 Jul 2012 23:21:14 +0200 [thread overview]
Message-ID: <20120723232114.54949dfe@arrakis> (raw)
Hi,
The Lwt team is happy to announce the release of Lwt 2.4.0. This
version fixes compatibility problems with OCaml 4.00 and contains a
few other enhancements and bug fixes.
You can download it at:
http://ocsigen.org/lwt/install
A description of changes is available at:
http://ocsigen.org/lwt/Lwt240
Here is a list of changes from the previous version (2.3.2):
* Reimplement Lwt_stream
** much simpler and more efficient
** do not use Weak
** add bounded push streams
* Add Lwt.async
* Add Lwt_preemptive.run_in_main
* Implement Lwt_unix.get_credentials on MacOS X/OpenBSD
* Ensure that on_cancel functions are executed first
* Better implementation of Lwt.cancel with more tests
* Simplify the API for unix jobs
* Better handling of the master lock in libev stubs
* Windows fixes/updates:
** pass -lws2_32 instead of ws2_32.lib if building with mingw
** fix a bug causing Lwt_unix.read/write to block when a socket
is not readable/writable
** port Lwt_process and Lwt_unix.system to windows
* Compatibility with ocaml 4.00:
** add O_SHARE_DELETE to Lwt_unix.open_flag
** add -package compiler-libs.toplevel for files using Toploop
* Do not use module Sys for signal handling to avoid
ocaml code to be called in a C thread
* Fix Lwt_unix.wrap_syscall: try instead of Lwt.catch
* Fix a dead-lock between lwt_unix_send_notification
and lwt_unix_recv_notifications
* Fix #277: add a function to return the Ssl.socket of a Lwt_ssl.socket
* Fix problems with C libraries detection/linking
--
Jérémie Dimino, for the Lwt team
reply other threads:[~2012-07-23 21:21 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=20120723232114.54949dfe@arrakis \
--to=jeremie@dimino.org \
--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).