| … | |
… | |
| 2 | |
2 | |
| 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 | |
|
|
8 | 4.1 |
|
|
9 | - incompatible change: $SIG{__DIE__} and $SIG{__WARN__} will now |
|
|
10 | be local to each coro (see Coro::State). |
|
|
11 | - possibly bring back 5.10 compatibility (untested). |
|
|
12 | - work around stupid (and wrong) warning on 5.10 :(. |
|
|
13 | - overlay the saved state over the context stack. This saves |
|
|
14 | a few hundred bytes per coroutine on average and also |
|
|
15 | speeds up context switching a bit. |
|
|
16 | - further tune default stack sizes. |
|
|
17 | - (more) correctly calculate stack usage in coro_rss. |
|
|
18 | - Coro::Storable::blocking_* did not properly lock |
|
|
19 | resulting in races between coroutines. |
|
|
20 | - added Coro::Storable::guard. |
|
|
21 | - stopping to trace a coroutine could destroy the cctx of |
|
|
22 | an unrelated coroutine. |
|
|
23 | - explain the relationship between Perl and C coroutines in |
|
|
24 | more detail in Coro::State. |
|
|
25 | - Coro::Util::inet_aton did not short-circuit dotted quad forms, |
|
|
26 | causing a fork per resolve. This also affected Coro::Socket. |
|
|
27 | - sped up Coro::Event next event handling by 15%, uses less memory. |
|
|
28 | |
|
|
29 | 4.03 Sat Oct 6 21:24:00 CEST 2007 |
|
|
30 | - added Coro::throw method. |
|
|
31 | - minor code cleanups. |
|
|
32 | |
|
|
33 | 4.02 Sat Oct 6 02:36:47 CEST 2007 |
|
|
34 | - fix a very minor per-coroutine memleak (a single codereference). |
|
|
35 | - fixed a bug where the currently in-use c context would be freed |
|
|
36 | prematurely (can happen only when programs change the stacksize |
|
|
37 | or use tracing). |
|
|
38 | - tracing can no longer keep a coro alive after it terminated. |
|
|
39 | - do static branch prediction in the common path for gcc. gives |
|
|
40 | about 2-5% speed improvement here. |
| 7 | |
41 | |
| 8 | 4.01 Fri Oct 5 22:10:49 CEST 2007 |
42 | 4.01 Fri Oct 5 22:10:49 CEST 2007 |
| 9 | - instead of recreating *a* standard output handle we simply |
43 | - instead of recreating *a* standard output handle we simply |
| 10 | use STDOUT, which is faster and hopefully more robust. |
44 | use STDOUT, which is faster and hopefully more robust. |
| 11 | |
45 | |
