| … | |
… | |
| 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 | - reset diehook when terminating from an async_pool as to not |
|
|
9 | trigger any __DIE__ handlers. |
|
|
10 | |
|
|
11 | 4.35 Sun Jan 13 04:14:13 CET 2008 |
|
|
12 | - "bt" debug command now displays any exceptions |
|
|
13 | from longmess and also skips the innermost |
|
|
14 | stackframes, giving more useufl output. |
|
|
15 | - allow backtraces in coroutines blocked in Coro::EV, |
|
|
16 | at a <1% speed hit. |
|
|
17 | - handle localising of $SIG{__WARN__} and __DIE__ |
|
|
18 | properly (with a proper amount of dirty hacking). |
|
|
19 | |
|
|
20 | 4.34 Sat Dec 22 17:49:53 CET 2007 |
|
|
21 | - upgrade to EV version 2.0 API. |
|
|
22 | |
|
|
23 | 4.33 Mon Dec 17 08:36:12 CET 2007 |
|
|
24 | - make Coro::AIO etc. loadable in the absence of EV. |
|
|
25 | |
|
|
26 | 4.32 Mon Dec 17 07:46:02 CET 2007 |
|
|
27 | - majorly improved Coro::Handle's performance with Coro::EV. |
|
|
28 | - implemented the until now mythical Coro::BDB module. |
|
|
29 | - specialcase EV in Coro::AIO and Coro::BDB for extra speed. |
|
|
30 | |
|
|
31 | 4.31 Wed Dec 5 12:32:39 CET 2007 |
|
|
32 | - remove warn statement form Coro::Util. |
|
|
33 | |
|
|
34 | 4.3 Tue Dec 4 20:33:14 CET 2007 |
|
|
35 | - calls to the idle function could cause stack corruption |
|
|
36 | when the stack changed. |
|
|
37 | - do no longer rely on the presence of EV::DNS if EV is used |
|
|
38 | (because it is gone), but instead take avdantage of EV::ADNS |
|
|
39 | if available. |
|
|
40 | - add ($) prototypes to all functions in Coro::Storable. |
|
|
41 | - use a conventional (safer) idle callback in Coro::EV. |
|
|
42 | - do accept quickly in Coro::Debug to avoid endless loops. |
|
|
43 | |
|
|
44 | 4.22 Fri Nov 30 16:04:04 CET 2007 |
|
|
45 | - really use optimised versions for Event and EV in Coro::Util |
|
|
46 | and Coro::Handle. |
|
|
47 | |
|
|
48 | 4.21 Sun Nov 25 10:48:59 CET 2007 |
|
|
49 | - fix a spurious memory read. |
|
|
50 | - Coro::EV no longer keeps the eventloop "alive". |
|
|
51 | |
|
|
52 | 4.2 Fri Nov 9 20:47:05 CET 2007 |
|
|
53 | - enable/disable tracing from a new coroutine, not a pooled one. |
|
|
54 | - fix a memleak in Coro::Event. |
|
|
55 | - removed killall call from fork_eval. |
|
|
56 | - made sure store_fd is already loaded so that fork_eval |
|
|
57 | does not have to parse autoload in each subprocess. |
|
|
58 | - only use assembly method if -O switch is in $Config{optimize}. |
|
|
59 | - add (optional) Coro::EV module, so far the best event loop module |
|
|
60 | directly supported by Coro. |
|
|
61 | - if the event model is EV, use EV::DNS to resolve |
|
|
62 | stuff in Coro::Util. |
|
|
63 | - don't get confused by multiple event notifications in Coro::Handle. |
|
|
64 | - initial support for EV (libevent interface). |
|
|
65 | - require Event and EV using configure_requires, to force their existance. |
|
|
66 | |
|
|
67 | 4.13 Wed Oct 24 07:26:45 CEST 2007 |
|
|
68 | - add Coro::Storable::blocking_thaw. |
|
|
69 | - use a vastly more complicated technique to localise |
|
|
70 | $SIG{__WARN/DIE__} that also works on perls <= 5.8.8. |
|
|
71 | - use a coroutine for the idle callback Coro::Event, |
|
|
72 | instead of running Event in the current coroutine context. |
|
|
73 | This also catches recursive invocations. |
|
|
74 | - actually report fork errors in gethostbyname and inet_aton. |
|
|
75 | |
|
|
76 | 4.11 Thu Oct 11 02:40:24 CEST 2007 |
|
|
77 | - port to threaded perls. |
|
|
78 | |
|
|
79 | 4.1 Thu Oct 11 02:38:16 CEST 2007 |
|
|
80 | - incompatible change: $SIG{__DIE__} and $SIG{__WARN__} will now |
|
|
81 | be local to each coro (see Coro::State). |
|
|
82 | - incompatible change: for very deep reasons, cede and cede_notself |
|
|
83 | cannot return anything, so nothing will be returned. |
|
|
84 | - possibly bring back 5.10 compatibility (untested). |
|
|
85 | - work around stupid (and wrong) warning on 5.10 :(. |
|
|
86 | - overlay the saved state over the context stack. This saves |
|
|
87 | a few hundred bytes per coroutine on average and also |
|
|
88 | speeds up context switching a bit. |
|
|
89 | - further tune default stack sizes. |
|
|
90 | - (more) correctly calculate stack usage in coro_rss. |
|
|
91 | - Coro::Storable::blocking_* did not properly lock |
|
|
92 | resulting in races between coroutines. |
|
|
93 | - added Coro::Storable::guard. |
|
|
94 | - stopping to trace a coroutine could destroy the cctx of |
|
|
95 | an unrelated coroutine. |
|
|
96 | - explain the relationship between Perl and C coroutines in |
|
|
97 | more detail in Coro::State. |
|
|
98 | - Coro::Util::inet_aton did not short-circuit dotted quad forms, |
|
|
99 | causing a fork per resolve. This also affected Coro::Socket. |
|
|
100 | - switch to a separate stack in $coro->call/eval to avoid |
|
|
101 | invalidating pointers. |
|
|
102 | |
|
|
103 | 4.03 Sat Oct 6 21:24:00 CEST 2007 |
|
|
104 | - added Coro::throw method. |
|
|
105 | - minor code cleanups. |
|
|
106 | |
|
|
107 | 4.02 Sat Oct 6 02:36:47 CEST 2007 |
| 9 | - fix a very minor per-coroutine memleak (a single codereference). |
108 | - fix a very minor per-coroutine memleak (a single codereference). |
| 10 | - fixed a bug where the currently in-use c context would be freed |
109 | - fixed a bug where the currently in-use c context would be freed |
| 11 | prematurely (can happen only when programs change the stacksize |
110 | prematurely (can happen only when programs change the stacksize |
| 12 | or use tracing). |
111 | or use tracing). |
| 13 | - tracing can no longer keep a coro alive after it terminated. |
112 | - tracing can no longer keep a coro alive after it terminated. |
