| … | |
… | |
| 2 | |
2 | |
| 3 | TODO: should explore PerlIO::coroaio (perl leaks like hell). |
3 | TODO: should explore PerlIO::coroaio (perl leaks like hell). |
| 4 | TODO: maybe implement a default message channel, very much like Erlang's |
4 | TODO: maybe implement a default message channel, very much like Erlang's |
| 5 | actor model (which is cool in a lot of important aspects (failures!), |
5 | actor model (which is cool in a lot of important aspects (failures!), |
| 6 | but very lacking in others (higher level ipc)). |
6 | but very lacking in others (higher level ipc)). |
|
|
7 | TODO: unready_all |
| 7 | |
8 | |
| 8 | TODO: CF_RUNNING makes sense only for Coros, not States |
9 | TODO: myhttpd header parsing |
| 9 | TODO: Coro::AnyEvent should only force detect in the idle hook. |
10 | - do not keep a reference to the argument itself in |
|
|
11 | Coro::Senmaphore::guard, as it could change later. |
|
|
12 | - support SO_RCVBUF/SO_SNDBUF nonstandard Coro::Socket options, |
|
|
13 | should support a prepare callback. |
|
|
14 | |
|
|
15 | 5.131 Mon Mar 16 23:20:37 CET 2009 |
|
|
16 | - implement and document Coro->suspend, Coro->resume. |
|
|
17 | - fix Coro::Select implementation to not (often) close |
|
|
18 | the passed file descriptors (testcase provided by pippijn). |
|
|
19 | |
|
|
20 | 5.13 Mon Dec 15 21:51:42 CET 2008 |
|
|
21 | - EXPERIMENTAL: implement dynamic winds (on_enter/on_leave). |
|
|
22 | - don't set diehook to C<undef> but instead to NULL, to avoid |
|
|
23 | spurious warnings. |
|
|
24 | - fix a lot of bugs in Coro::SemaphoreSet. |
|
|
25 | - Coro::SemaphoreSet will less often create a semaphore needlessly. |
|
|
26 | - add Coro::SemaphoreSet::count and wait methods. |
|
|
27 | - take advantage of the new Guard module. |
|
|
28 | - deprecate Coro::guard. |
|
|
29 | - try to fix the dreaded 01_unblock tests once more. I hate it when |
|
|
30 | testsuites need more fixing than the code they are supposed to test. |
|
|
31 | - croak in more cases when a required callback isn't resolvable. |
|
|
32 | - fix some minor issues in Coro::State->call/eval. |
|
|
33 | - use current coroutine context instead of a temporary one |
|
|
34 | when temporarily switching to another coroutine. |
|
|
35 | - do not call C-level on_destroy handlers during global destruction, |
|
|
36 | to avoid needless segfaults. |
|
|
37 | |
|
|
38 | 5.12 Sun Dec 7 13:30:38 CET 2008 |
| 10 | - add default config for MirOS, which seems to be a bug-to-bug |
39 | - add default config for MirOS, which seems to be a bug-to-bug |
| 11 | compatible fork of openbsd ("world domination by releasing |
40 | compatible fork of openbsd ("world domination by releasing |
| 12 | openbsd cvs before the openbsd folks do it" or so :). |
41 | openbsd cvs before the openbsd folks do it" or so :). |
| 13 | - free_padlist did destroy the names pad, not good, but didn't |
42 | - free_padlist did destroy the names pad, not good, but didn't |
| 14 | seem to bother perl - this could fix issues such as eval "" |
43 | seem to bother perl - this could fix issues such as eval "" |
| 15 | inside a function called form multiple coroutines. |
44 | inside a function called from multiple coroutines. |
| 16 | - use a different method to detect destruction time. |
45 | - use a different method to detect destruction time. |
| 17 | - be more careful when freeing padlists just before global |
46 | - be more careful when freeing padlists just before global |
| 18 | destruction. |
47 | destruction. |
| 19 | - fixed and expanded the call/cc example. |
48 | - fixed and expanded the call/cc example. |
| 20 | - renamed _terminate to _coro_run. |
49 | - renamed _terminate to _coro_run. |
|
|
50 | - new method Coro::Channel->shutdown. |
|
|
51 | - try pthreads on openbsd <4.4 (broken sigaltstack, will |
|
|
52 | pthreads fare better?). |
|
|
53 | - be less picky about destroying "a" running coroutine. |
| 21 | |
54 | |
| 22 | 5.11 Tue Nov 25 21:49:05 CET 2008 |
55 | 5.11 Tue Nov 25 21:49:05 CET 2008 |
| 23 | - DEBUGGING in 5.10.0 is a mess: it constantly flags perfectly |
56 | - DEBUGGING in 5.10.0 is a mess: it constantly flags perfectly |
| 24 | working code with failed assertions, introducing more bugs than |
57 | working code with failed assertions, introducing more bugs than |
| 25 | it fixes, requiring elaborate workarounds :( |
58 | it fixes, requiring elaborate workarounds :( |
