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