--- AnyEvent/Changes 2009/09/28 17:30:53 1.350 +++ AnyEvent/Changes 2009/12/04 16:31:57 1.361 @@ -1,7 +1,34 @@ Revision history for Perl extension AnyEvent. +TODO: inet_aton does not actually deliver ipv6 addresses + - downgrade-or-fail in AnyEvent::Handle::push_write, to + diagnose encoding failures earlier and more succinctly. + (this works around bugs in perl, throwing away encoding info + when passing scalar data to extensions). + - add more examples to AnyEvent::Socket manpage. + - upgrade internal warning set to the same as common::sense 2.03. + +5.21 Thu Nov 19 02:48:47 CET 2009 + - fix a problem where socket constants were called with parameters + (spotted by David Friedland). + - fork_call never use'd POSIX (reported by Daisuke Maki). + - improve perl 5.6 compatibility further (but it still won't work + unless you rip out everything but the core). + - prefer Net::DNS::Resolver over ipconfig, if installed, on win32. + uses 10MB of RAM, but doesn't open a console window. *sigh*. + +5.202 Wed Oct 14 22:35:44 CEST 2009 + - AnyEvent::DNS would unexpectedly clobber $_ under windows + (analysed by Matthias Waldorf). + - AnyEvent::Handle::run_cmd can now pass the PID of the + newly-created process, which is much less useful than it might + sound (based on patch by Yann Kerherve). + +5.201 Tue Sep 29 12:09:25 CEST 2009 - AnyEvent:Handle::on_starttls/on_stoptls methods were broken (reported by Torsten Foertsch). + - common::sense 2.0 could cause tcp_server to throw an exception + (analysed by elmex). 5.2 Mon Sep 14 07:04:49 CEST 2009 - INCOMPATIBLE CHANGE: do no longer support register_read_type @@ -106,7 +133,7 @@ 4.881 Tue Jul 28 12:51:53 CEST 2009 - work around a bug in local in pre-5.10 perls, causing AnyEvent::Handle to recurse when it should not - (analyzed by elmex). + (analysed by elmex). 4.88 Tue Jul 28 04:04:37 CEST 2009 - re-bless the handle into a dummy package after calling @@ -341,11 +368,11 @@ - fixed a great number of bugs and corner cases in AnyEvent::Handle: - fix a bug in where in SSL connect mode, the client would first wait for some data by the server and - otherwise hang. (reported and analyzed in an absolutely + otherwise hang. (reported and analysed in an absolutely exemplary manner by Adam Rosenstein). - fix a bug in where SSL EOF would not be treated as stream EOF, putting the connection into a hung state. - (reported and analyzed in an absolutely exemplary manner by Adam + (reported and analysed in an absolutely exemplary manner by Adam Rosenstein). - fix a potential segfault when the TLS context would go missing in a read callback (e.g. due to stoptls) -