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