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

Comparing Coro/Changes (file contents):
Revision 1.459 by root, Sat Nov 22 15:48:43 2008 UTC vs.
Revision 1.474 by root, Sat Dec 6 00:55:59 2008 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines