ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/Coro/Changes
(Generate patch)

Comparing Coro/Changes (file contents):
Revision 1.330 by root, Sat Apr 5 22:38:26 2008 UTC vs.
Revision 1.343 by root, Fri May 9 22:29:05 2008 UTC

2 2
3TODO: should explore PerlIO::via::CoroCede and PerlIO::via::CoroAIO. 3TODO: should explore PerlIO::via::CoroCede and PerlIO::via::CoroAIO.
4TODO: maybe implement a default message channel, very much like Erlang's 4TODO: 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
8 TODO: Coro::AnyEvent
9 - completely reworked the Coro manpage.
10 - added Coro::AnyEvent, generic event loop integration.
11 - implement cancel, ready and kill commands in Coro::Debug.
12 - document find_coro in Coro::Debug.
13 - incompatible change: rename has_stack to has_cctx.
14
154.6 Sat Apr 26 10:05:14 CEST 2008
16 - INCOMPATIBLE CHANGE: sub/code attributes are no longer supported
17 by the Coro module. It was a mistake to have it in the first place.
18 - (experimental) support for activestate perl 5.10 (method "w").
19 - (experimental) support for strawberry perl (method "a").
20 - coro_sigelem_set did not return a value although it had to,
21 actual impact unknown.
22
234.51 Mon Apr 14 13:28:27 CEST 2008
24 - make it compile again on 5.8.
25
264.50 Thu Apr 10 09:43:17 CEST 2008
27 - I did it twice! (see 4.49).
28
294.49 Sun Apr 6 21:23:31 CEST 2008
30 - grr, instead of compiling the recent changes on 5.10 only they
31 were compiled on 5.8 only.
32
334.48 Sun Apr 6 20:36:46 CEST 2008
34 - allow coroutine switches during eval's under 5.10.x, as it seems
35 the parser is a per-interpreter option now, so this is safe
36 (this might fix the odd crashing bug).
37 - drop support for 5.9.x versions: they are dead, jim.
7 38
84.47 Sun Apr 6 00:37:52 CEST 2008 394.47 Sun Apr 6 00:37:52 CEST 2008
9 - force cctx allocation on API calls: we know we need to force one 40 - force cctx allocation on API calls: we know we need to force one
10 and gcc actually manages to confuse our heuristic nowadays, 41 and gcc actually manages to confuse our heuristic nowadays,
11 leading to crashes and worse. 42 leading to crashes and worse.

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines