--- Coro/Changes 2007/10/05 20:11:25 1.256 +++ Coro/Changes 2007/12/27 21:32:15 1.308 @@ -5,9 +5,108 @@ (which is cool in a lot of important aspects (failures!), but very lacking in others (higher level ipc)). + - "bt" debug command now displays any exceptions + from longmess. + +4.34 Sat Dec 22 17:49:53 CET 2007 + - upgrade to EV version 2.0 API. + +4.33 Mon Dec 17 08:36:12 CET 2007 + - make Coro::AIO etc. loadable in the absence of EV. + +4.32 Mon Dec 17 07:46:02 CET 2007 + - majorly improved Coro::Handle's performance with Coro::EV. + - implemented the until now mythical Coro::BDB module. + - specialcase EV in Coro::AIO and Coro::BDB for extra speed. + +4.31 Wed Dec 5 12:32:39 CET 2007 + - remove warn statement form Coro::Util. + +4.3 Tue Dec 4 20:33:14 CET 2007 + - calls to the idle function could cause stack corruption + when the stack changed. + - do no longer rely on the presence of EV::DNS if EV is used + (because it is gone), but instead take avdantage of EV::ADNS + if available. + - add ($) prototypes to all functions in Coro::Storable. + - use a conventional (safer) idle callback in Coro::EV. + - do accept quickly in Coro::Debug to avoid endless loops. + +4.22 Fri Nov 30 16:04:04 CET 2007 + - really use optimised versions for Event and EV in Coro::Util + and Coro::Handle. + +4.21 Sun Nov 25 10:48:59 CET 2007 + - fix a spurious memory read. + - Coro::EV no longer keeps the eventloop "alive". + +4.2 Fri Nov 9 20:47:05 CET 2007 + - enable/disable tracing from a new coroutine, not a pooled one. + - fix a memleak in Coro::Event. + - removed killall call from fork_eval. + - made sure store_fd is already loaded so that fork_eval + does not have to parse autoload in each subprocess. + - only use assembly method if -O switch is in $Config{optimize}. + - add (optional) Coro::EV module, so far the best event loop module + directly supported by Coro. + - if the event model is EV, use EV::DNS to resolve + stuff in Coro::Util. + - don't get confused by multiple event notifications in Coro::Handle. + - initial support for EV (libevent interface). + - require Event and EV using configure_requires, to force their existance. + +4.13 Wed Oct 24 07:26:45 CEST 2007 + - add Coro::Storable::blocking_thaw. + - use a vastly more complicated technique to localise + $SIG{__WARN/DIE__} that also works on perls <= 5.8.8. + - use a coroutine for the idle callback Coro::Event, + instead of running Event in the current coroutine context. + This also catches recursive invocations. + - actually report fork errors in gethostbyname and inet_aton. + +4.11 Thu Oct 11 02:40:24 CEST 2007 + - port to threaded perls. + +4.1 Thu Oct 11 02:38:16 CEST 2007 + - incompatible change: $SIG{__DIE__} and $SIG{__WARN__} will now + be local to each coro (see Coro::State). + - incompatible change: for very deep reasons, cede and cede_notself + cannot return anything, so nothing will be returned. + - possibly bring back 5.10 compatibility (untested). + - work around stupid (and wrong) warning on 5.10 :(. + - overlay the saved state over the context stack. This saves + a few hundred bytes per coroutine on average and also + speeds up context switching a bit. + - further tune default stack sizes. + - (more) correctly calculate stack usage in coro_rss. + - Coro::Storable::blocking_* did not properly lock + resulting in races between coroutines. + - added Coro::Storable::guard. + - stopping to trace a coroutine could destroy the cctx of + an unrelated coroutine. + - explain the relationship between Perl and C coroutines in + more detail in Coro::State. + - Coro::Util::inet_aton did not short-circuit dotted quad forms, + causing a fork per resolve. This also affected Coro::Socket. + - switch to a separate stack in $coro->call/eval to avoid + invalidating pointers. + +4.03 Sat Oct 6 21:24:00 CEST 2007 + - added Coro::throw method. + - minor code cleanups. + +4.02 Sat Oct 6 02:36:47 CEST 2007 + - fix a very minor per-coroutine memleak (a single codereference). + - fixed a bug where the currently in-use c context would be freed + prematurely (can happen only when programs change the stacksize + or use tracing). + - tracing can no longer keep a coro alive after it terminated. + - do static branch prediction in the common path for gcc. gives + about 2-5% speed improvement here. + 4.01 Fri Oct 5 22:10:49 CEST 2007 - - use a different, less descriptive but hopefully more robust way - to create the stdout glob for a newly created coroutine. + - instead of recreating *a* standard output handle we simply + use STDOUT, which is faster and hopefully more robust. 4.0 Fri Oct 5 12:56:00 CEST 2007 - incompatibly changed Coro::Storable::freeze.