| … | |
… | |
| 3 | TODO: should explore PerlIO::via::CoroCede and PerlIO::via::CoroAIO. |
3 | TODO: should explore PerlIO::via::CoroCede and PerlIO::via::CoroAIO. |
| 4 | TODO: maybe implement a default message channel, very much like Erlang |
4 | TODO: maybe implement a default message channel, very much like Erlang |
| 5 | (which is cool in a lot of important aspects (failures!), |
5 | (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 | 4.02 |
8 | - fix a spurious memory read. |
|
|
9 | - Coro::EV no longer keeps the eventloop "alive". |
|
|
10 | |
|
|
11 | 4.2 Fri Nov 9 20:47:05 CET 2007 |
|
|
12 | - enable/disable tracing from a new coroutine, not a pooled one. |
|
|
13 | - fix a memleak in Coro::Event. |
|
|
14 | - removed killall call from fork_eval. |
|
|
15 | - made sure store_fd is already loaded so that fork_eval |
|
|
16 | does not have to parse autoload in each subprocess. |
|
|
17 | - only use assembly method if -O switch is in $Config{optimize}. |
|
|
18 | - add (optional) Coro::EV module, so far the best event loop module |
|
|
19 | directly supported by Coro. |
|
|
20 | - if the event model is EV, use EV::DNS to resolve |
|
|
21 | stuff in Coro::Util. |
|
|
22 | - don't get confused by multiple event notifications in Coro::Handle. |
|
|
23 | - initial support for EV (libevent interface). |
|
|
24 | - require Event and EV using configure_requires, to force their existance. |
|
|
25 | |
|
|
26 | 4.13 Wed Oct 24 07:26:45 CEST 2007 |
|
|
27 | - add Coro::Storable::blocking_thaw. |
|
|
28 | - use a vastly more complicated technique to localise |
|
|
29 | $SIG{__WARN/DIE__} that also works on perls <= 5.8.8. |
|
|
30 | - use a coroutine for the idle callback Coro::Event, |
|
|
31 | instead of running Event in the current coroutine context. |
|
|
32 | This also catches recursive invocations. |
|
|
33 | - actually report fork errors in gethostbyname and inet_aton. |
|
|
34 | |
|
|
35 | 4.11 Thu Oct 11 02:40:24 CEST 2007 |
|
|
36 | - port to threaded perls. |
|
|
37 | |
|
|
38 | 4.1 Thu Oct 11 02:38:16 CEST 2007 |
|
|
39 | - incompatible change: $SIG{__DIE__} and $SIG{__WARN__} will now |
|
|
40 | be local to each coro (see Coro::State). |
|
|
41 | - incompatible change: for very deep reasons, cede and cede_notself |
|
|
42 | cannot return anything, so nothing will be returned. |
|
|
43 | - possibly bring back 5.10 compatibility (untested). |
|
|
44 | - work around stupid (and wrong) warning on 5.10 :(. |
|
|
45 | - overlay the saved state over the context stack. This saves |
|
|
46 | a few hundred bytes per coroutine on average and also |
|
|
47 | speeds up context switching a bit. |
|
|
48 | - further tune default stack sizes. |
|
|
49 | - (more) correctly calculate stack usage in coro_rss. |
|
|
50 | - Coro::Storable::blocking_* did not properly lock |
|
|
51 | resulting in races between coroutines. |
|
|
52 | - added Coro::Storable::guard. |
|
|
53 | - stopping to trace a coroutine could destroy the cctx of |
|
|
54 | an unrelated coroutine. |
|
|
55 | - explain the relationship between Perl and C coroutines in |
|
|
56 | more detail in Coro::State. |
|
|
57 | - Coro::Util::inet_aton did not short-circuit dotted quad forms, |
|
|
58 | causing a fork per resolve. This also affected Coro::Socket. |
|
|
59 | - switch to a separate stack in $coro->call/eval to avoid |
|
|
60 | invalidating pointers. |
|
|
61 | |
|
|
62 | 4.03 Sat Oct 6 21:24:00 CEST 2007 |
|
|
63 | - added Coro::throw method. |
|
|
64 | - minor code cleanups. |
|
|
65 | |
|
|
66 | 4.02 Sat Oct 6 02:36:47 CEST 2007 |
| 9 | - fix a very minor per-coroutine memleak (a single codereference). |
67 | - fix a very minor per-coroutine memleak (a single codereference). |
| 10 | - fixed a bug where the currently in-use c context would be freed |
68 | - fixed a bug where the currently in-use c context would be freed |
| 11 | prematurely (can happen only when programs change the stacksize |
69 | prematurely (can happen only when programs change the stacksize |
| 12 | or use tracing). |
70 | or use tracing). |
| 13 | - tracing can no longer keep a coro alive after it terminated. |
71 | - tracing can no longer keep a coro alive after it terminated. |
