1 | Revision history for Perl extension Coro. |
1 | Revision history for Perl extension Coro. |
2 | |
2 | |
|
|
3 | TODO: better (earlier) error messages on broken transfer's |
|
|
4 | |
3 | 3.0 |
5 | 3. |
|
|
6 | - INCOMPATIBLE CHANGE: $/ is now per-coroutine. |
|
|
7 | - incompatible change: transfer flags are now per-state. |
|
|
8 | - give a better error message on deadlock. |
|
|
9 | - document Coro::nready. |
|
|
10 | - enhanced testsuite. |
|
|
11 | |
|
|
12 | 3.01 Sun Dec 3 23:47:42 CET 2006 |
|
|
13 | - forgot to include Coro::Timer. |
|
|
14 | |
|
|
15 | 3.0 Sun Dec 3 22:57:25 CET 2006 |
4 | - the "FINALLY COMPLETELY STABLE" release (coming soon: |
16 | - the "FINALLY COMPLETELY STABLE" release (coming soon: |
5 | the "FAMOUS LAST WORDS" release). |
17 | the "FAMOUS LAST WORDS" release). |
6 | - implement a new stack sharing algorithm, which uses a stack |
18 | - implement a new stack sharing algorithm, which uses a stack |
7 | pool (size currently hardcoded). |
19 | pool (size currently hardcoded). |
8 | - make stack sharing mandatory (it no longer uses a heuristic). |
20 | - make stack sharing mandatory (it no longer uses a heuristic). |
9 | - eval/die no longer cause weird problems under heavy use. |
21 | - eval/die no longer cause weird problems under heavy use. |
10 | - Coro::Event could cause livelocks if it was used but |
22 | - Coro::Event could cause livelocks if it was used but |
11 | no Coro::Event watchers were used. |
23 | no Coro::Event watchers were used. |
12 | - Coro::Event now uses asynccheck as prepare does not |
24 | - Coro::Event now uses asynccheck as prepare does not |
13 | check for changed watchers. |
25 | check for changed watchers. |
|
|
26 | - Coro::Event allows multiple waiting coros and will wake up one |
|
|
27 | per event. |
14 | - Coro::Event should be cleaner and more efficient now. |
28 | - Coro::Event should be cleaner and more efficient now. |
15 | - new utility function Coro::unblock_sub. |
29 | - new utility function Coro::unblock_sub. |
16 | - document the sad fact that Event is no longer reentrant. |
30 | - document the sad fact that Event is no longer reentrant. |
17 | - putting a coroutine into the ready queue twice could under |
31 | - putting a coroutine into the ready queue twice could under |
18 | some circumstances lead to stack corruption. |
32 | some circumstances lead to stack corruption. |