| 1 | Revision history for Perl extension Coro. |
1 | Revision history for Perl extension Coro. |
| 2 | |
2 | |
|
|
3 | TODO: transfer flags must be per state |
|
|
4 | TODO: better (earlier) error messages on broken transfer's |
|
|
5 | |
| 3 | 3.0 |
6 | 3. |
|
|
7 | - INCOMPATIBLE CHANGE: $/ is now per-coroutine. |
|
|
8 | - incompatible change: transfer flags are now per-state. |
|
|
9 | - give a better error message on deadlock. |
|
|
10 | - document Coro::nready. |
|
|
11 | - enhanced testsuite. |
|
|
12 | |
|
|
13 | 3.01 Sun Dec 3 23:47:42 CET 2006 |
|
|
14 | - forgot to include Coro::Timer. |
|
|
15 | |
|
|
16 | 3.0 Sun Dec 3 22:57:25 CET 2006 |
| 4 | - the "FINALLY COMPLETELY STABLE" release (coming soon: |
17 | - the "FINALLY COMPLETELY STABLE" release (coming soon: |
| 5 | the "FAMOUS LAST WORDS" release). |
18 | the "FAMOUS LAST WORDS" release). |
| 6 | - implement a new stack sharing algorithm. |
19 | - implement a new stack sharing algorithm, which uses a stack |
|
|
20 | pool (size currently hardcoded). |
| 7 | - make stack sharing mandatory (it no longer uses a heuristic). |
21 | - make stack sharing mandatory (it no longer uses a heuristic). |
| 8 | - eval/die no longer cause weird problems under heavy use. |
22 | - eval/die no longer cause weird problems under heavy use. |
| 9 | - Coro::Event could cause livelocks if it was used but |
23 | - Coro::Event could cause livelocks if it was used but |
| 10 | no Coro::Event watchers were used. |
24 | no Coro::Event watchers were used. |
|
|
25 | - Coro::Event now uses asynccheck as prepare does not |
|
|
26 | check for changed watchers. |
|
|
27 | - Coro::Event allows multiple waiting coros and will wake up one |
|
|
28 | per event. |
| 11 | - Coro::Event should be cleaner and more efficient now. |
29 | - Coro::Event should be cleaner and more efficient now. |
|
|
30 | - new utility function Coro::unblock_sub. |
| 12 | - document the sad fact that Event is no longer reentrant. |
31 | - document the sad fact that Event is no longer reentrant. |
| 13 | - putting a coroutine into the ready queue twice could under |
32 | - putting a coroutine into the ready queue twice could under |
| 14 | some circumstances lead to stack corruption. |
33 | some circumstances lead to stack corruption. |
| 15 | - minor incompatibility: subclassing Coro::State is supported |
34 | - minor incompatibility: subclassing Coro::State is supported |
| 16 | directly now without going through a _coro_state member. |
35 | directly now without going through a _coro_state member. |
| … | |
… | |
| 20 | - removed timers from Coro::Timer -> use AnyEvent instead. |
39 | - removed timers from Coro::Timer -> use AnyEvent instead. |
| 21 | - replaced Coro::idle coroutine by (cleaner) idle handler. |
40 | - replaced Coro::idle coroutine by (cleaner) idle handler. |
| 22 | - updated to newest libcoro. |
41 | - updated to newest libcoro. |
| 23 | - implement enhanced support for valgrind. |
42 | - implement enhanced support for valgrind. |
| 24 | - implement is_ready and return value for ready. |
43 | - implement is_ready and return value for ready. |
|
|
44 | - removed Coro::Cont, it was a misnomer (it's generators), |
|
|
45 | and it was somewhat annoying to get it right. Will come back |
|
|
46 | if somebody asks for it :) |
| 25 | - many ->wait methods and Coro::Event could return |
47 | - many ->wait methods and Coro::Event could return |
| 26 | spuriously without the event having happened. |
48 | spuriously without the event having happened. |
| 27 | |
49 | |
| 28 | 2.5 Tue Nov 7 12:22:33 CET 2006 |
50 | 2.5 Tue Nov 7 12:22:33 CET 2006 |
| 29 | - made Coro::Util, Coro::Select, Coro::Handle and Coro::Socket |
51 | - made Coro::Util, Coro::Select, Coro::Handle and Coro::Socket |
