| … | |
… | |
| 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 | |
7 | |
|
|
8 | 5.12 Sun Dec 7 13:30:38 CET 2008 |
| 8 | - add default config for MirOS, which seems to be a bug-to-bug |
9 | - add default config for MirOS, which seems to be a bug-to-bug |
| 9 | compatible fork of openbsd ("world domination by releasing |
10 | compatible fork of openbsd ("world domination by releasing |
| 10 | openbsd cvs before the openbsd folks do it" or so :). |
11 | openbsd cvs before the openbsd folks do it" or so :). |
| 11 | - free_padlist did destroy the names pad, not good, but didn't |
12 | - free_padlist did destroy the names pad, not good, but didn't |
| 12 | seem to bother perl. |
13 | seem to bother perl - this could fix issues such as eval "" |
|
|
14 | inside a function called form multiple coroutines. |
| 13 | - use a different method to detect destruction time. |
15 | - use a different method to detect destruction time. |
| 14 | - be more careful when freeing padlists just before global |
16 | - be more careful when freeing padlists just before global |
| 15 | destruction. |
17 | destruction. |
|
|
18 | - fixed and expanded the call/cc example. |
|
|
19 | - renamed _terminate to _coro_run. |
|
|
20 | - new method Coro::Channel->shutdown. |
|
|
21 | - try pthreads on openbsd <4.4 (broken sigaltstack, will |
|
|
22 | pthreads fare better?). |
|
|
23 | - be less picky about destroying "a" running coroutine. |
| 16 | |
24 | |
| 17 | 5.11 Tue Nov 25 21:49:05 CET 2008 |
25 | 5.11 Tue Nov 25 21:49:05 CET 2008 |
| 18 | - DEBUGGING in 5.10.0 is a mess: it constantly flags perfectly |
26 | - DEBUGGING in 5.10.0 is a mess: it constantly flags perfectly |
| 19 | working code with failed assertions, introducing more bugs than |
27 | working code with failed assertions, introducing more bugs than |
| 20 | it fixes, requiring elaborate workarounds :( |
28 | it fixes, requiring elaborate workarounds :( |
