--- Coro/Changes 2006/12/01 19:41:06 1.167 +++ Coro/Changes 2006/12/25 13:25:55 1.185 @@ -1,6 +1,37 @@ Revision history for Perl extension Coro. -3.0 +TODO: better (earlier) error messages on broken transfer's + + - fix nice adding, not subtracting, from priority. + - fix ->prio and api_is_ready (patch by Mark Hinds). + +3.2 Fri Dec 22 05:07:09 CET 2006 + - improve portability to slightly older perls. + - use cleaner coroutine destruction. + - simplify configuration for users. + - optionally (unrecommended) prefer perl functions over + their coro replacements. + +3.11 Tue Dec 5 13:11:24 CET 2006 + - fixed some bogus assert's, but as perl.h disables assert even + without NDEBUG (thank you very much), not too many people should + notice (that did include myself). Andreas König noticed, though :) + - do not save/restore PL_sortcxix on >= 5.9.x, it doesn't seem to have + it. Also noticed by Andreas König :) + - save/restore tainted status. + - verified to pass the testsuite on my 5.9.5. + +3.1 Mon Dec 4 23:03:40 CET 2006 + - INCOMPATIBLE CHANGE: $/ is now per-coroutine (but slow). + - incompatible change: transfer flags are now per-state. + - give a better error message on deadlock. + - document Coro::nready. + - enhanced testsuite. + +3.01 Sun Dec 3 23:47:42 CET 2006 + - forgot to include Coro::Timer. + +3.0 Sun Dec 3 22:57:25 CET 2006 - the "FINALLY COMPLETELY STABLE" release (coming soon: the "FAMOUS LAST WORDS" release). - implement a new stack sharing algorithm, which uses a stack @@ -11,6 +42,8 @@ no Coro::Event watchers were used. - Coro::Event now uses asynccheck as prepare does not check for changed watchers. + - Coro::Event allows multiple waiting coros and will wake up one + per event. - Coro::Event should be cleaner and more efficient now. - new utility function Coro::unblock_sub. - document the sad fact that Event is no longer reentrant. @@ -26,6 +59,9 @@ - updated to newest libcoro. - implement enhanced support for valgrind. - implement is_ready and return value for ready. + - removed Coro::Cont, it was a misnomer (it's generators), + and it was somewhat annoying to get it right. Will come back + if somebody asks for it :) - many ->wait methods and Coro::Event could return spuriously without the event having happened.