| … | |
… | |
| 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 | TODO: Coro/Intro |
8 | TODO: CF_RUNNING makes sense only for Coros, not States |
|
|
9 | TODO: Coro::AnyEvent should only force detect in the idle hook. |
|
|
10 | - add default config for MirOS, which seems to be a bug-to-bug |
|
|
11 | compatible fork of openbsd ("world domination by releasing |
|
|
12 | openbsd cvs before the openbsd folks do it" or so :). |
|
|
13 | - free_padlist did destroy the names pad, not good, but didn't |
|
|
14 | seem to bother perl - this could fix issues such as eval "" |
|
|
15 | inside a function called form multiple coroutines. |
|
|
16 | - use a different method to detect destruction time. |
|
|
17 | - be more careful when freeing padlists just before global |
|
|
18 | destruction. |
|
|
19 | - fixed and expanded the call/cc example. |
|
|
20 | - renamed _terminate to _coro_run. |
|
|
21 | |
|
|
22 | 5.11 Tue Nov 25 21:49:05 CET 2008 |
|
|
23 | - DEBUGGING in 5.10.0 is a mess: it constantly flags perfectly |
|
|
24 | working code with failed assertions, introducing more bugs than |
|
|
25 | it fixes, requiring elaborate workarounds :( |
|
|
26 | |
|
|
27 | 5.1 Mon Nov 24 08:54:59 CET 2008 |
|
|
28 | - wrote a small introductory tutorial - Coro::Intro. |
| 9 | - convert Coro::Timer, Coro::Select and Coro::Util to rouse API. |
29 | - convert Coro::Timer, Coro::Select and Coro::Util to rouse API. |
| 10 | - Coro::Select did errornously dup the file descriptors |
30 | - Coro::Select did errornously dup the file descriptors |
| 11 | and didn't work with all AnyEvent backends. |
31 | and didn't work with all AnyEvent backends. |
|
|
32 | - Coro::Select wasn't imported correctly form Coro::LWP, causing blocking |
|
|
33 | LWP data transfers. |
| 12 | - disassociate c contexts from coro objects - this is agruably more |
34 | - disassociate c contexts from coro objects - this is agruably more |
| 13 | correct, but mostly allows sharing of cctxs between coro and state |
35 | correct, but mostly allows sharing of cctxs between coro and state |
| 14 | objects, for added memory savings and speed increases. |
36 | objects, for added memory savings and speed increases. |
| 15 | - bumped $Coro::POOL_RSS up to 32kb by default. |
37 | - bumped $Coro::POOL_RSS up to 32kb by default. |
| 16 | - no longer set the optype to OP_CUSTOM, as B::* understandably |
38 | - no longer set the optype to OP_CUSTOM, as B::* understandably |
| 17 | doesn't like this very much (and we *are* a type of entersub). |
39 | doesn't like this very much (and we *are* a type of entersub). |
| 18 | - implement state cloning, just to prove that call/cc can be done. |
40 | - implement state cloning, just to prove that call/cc can be done. |
|
|
41 | - automatically load Coro::AnyEvent in Coro::Handle. |
|
|
42 | - wrap ->cancel calls in eval inside Coro::Handle as EV watchers |
|
|
43 | do not have this method (and don't need it either). |
|
|
44 | - speed up generic anyevent methods in Coro::Handle by using rouse |
|
|
45 | callbacks. |
|
|
46 | - allow coroutines in $Coro::IDLE, speeding up Coro::AnyEvent and |
|
|
47 | others. It also makes the debugger happier, as you can trace |
|
|
48 | through the idle threads now. |
|
|
49 | - add comppad_name* and hints ($^H, %^H) to per-thread variables. |
|
|
50 | - eg/event was pretty broken. |
| 19 | - better 5.8.6 compatibility. |
51 | - better 5.8.6 compatibility. |
| 20 | |
52 | |
| 21 | 5.0 Thu Nov 20 10:35:05 CET 2008 |
53 | 5.0 Thu Nov 20 10:35:05 CET 2008 |
| 22 | - NEW ARCHITECTURE: use the latest 4.x version if you experience |
54 | - NEW ARCHITECTURE: use the latest 4.x version if you experience |
| 23 | stability issues. |
55 | stability issues. |
