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

Comparing Coro/Changes (file contents):
Revision 1.449 by root, Thu Nov 20 07:12:41 2008 UTC vs.
Revision 1.468 by root, Thu Nov 27 12:20:31 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
85.0 8 - add default config for MirOS, which seems to be a bug-to-bug
9 compatible fork of openbsd ("world domination by releasing
10 openbsd cvs before the openbsd folks do it" or so :).
11 - free_padlist did destroy the names pad, not good, but didn't
12 seem to bother perl.
13 - use a different method to detect destruction time.
14 - be more careful when freeing padlists just before global
15 destruction.
16
175.11 Tue Nov 25 21:49:05 CET 2008
18 - DEBUGGING in 5.10.0 is a mess: it constantly flags perfectly
19 working code with failed assertions, introducing more bugs than
20 it fixes, requiring elaborate workarounds :(
21
225.1 Mon Nov 24 08:54:59 CET 2008
23 - wrote a small introductory tutorial - Coro::Intro.
24 - convert Coro::Timer, Coro::Select and Coro::Util to rouse API.
25 - Coro::Select did errornously dup the file descriptors
26 and didn't work with all AnyEvent backends.
27 - Coro::Select wasn't imported correctly form Coro::LWP, causing blocking
28 LWP data transfers.
29 - disassociate c contexts from coro objects - this is agruably more
30 correct, but mostly allows sharing of cctxs between coro and state
31 objects, for added memory savings and speed increases.
32 - bumped $Coro::POOL_RSS up to 32kb by default.
33 - no longer set the optype to OP_CUSTOM, as B::* understandably
34 doesn't like this very much (and we *are* a type of entersub).
35 - implement state cloning, just to prove that call/cc can be done.
36 - automatically load Coro::AnyEvent in Coro::Handle.
37 - wrap ->cancel calls in eval inside Coro::Handle as EV watchers
38 do not have this method (and don't need it either).
39 - speed up generic anyevent methods in Coro::Handle by using rouse
40 callbacks.
41 - allow coroutines in $Coro::IDLE, speeding up Coro::AnyEvent and
42 others. It also makes the debugger happier, as you can trace
43 through the idle threads now.
44 - add comppad_name* and hints ($^H, %^H) to per-thread variables.
45 - eg/event was pretty broken.
46 - better 5.8.6 compatibility.
47
485.0 Thu Nov 20 10:35:05 CET 2008
9 - NEW ARCHITECTURE: use the latest 4.x version if you experience 49 - NEW ARCHITECTURE: use the latest 4.x version if you experience
10 stability issues. 50 stability issues.
11 - bump API version to 7 - all dependents must be recompiled. 51 - bump API version to 7 - all dependents must be recompiled.
12 - removed timed_* functions - they were not being used anyways 52 - removed timed_* functions - they were not being used anyways
13 and should be replaced by a more generic mechanism - 53 and should be replaced by a more generic mechanism -
14 and were annoying to support anyways :) 54 and were annoying to support anyways :)
15 - removed SemaphoreSet's waiter method - use sem instead. 55 - removed SemaphoreSet's waiter method - use sem method instead.
16 - Coro::Semaphore->adjust didn't correctly wake up enough waiters. 56 - Coro::Semaphore->adjust didn't correctly wake up enough waiters.
17 - async_pool did free a scalar value twice 57 - async_pool did free a scalar value twice
18 ("Attempt to unreference..."). 58 ("Attempt to unreference...").
19 - fix a disastrous bug in the readline optimisation
20 introduced in 4.801.
21 - fix a longstanding bug where calling terminate on a coro that 59 - fix a longstanding bug where calling terminate on a coro that
22 was waiting for a semaphore that was just becoming available 60 was waiting for a semaphore that was just becoming available
23 would cause a deadlock (semaphore would get into a state where 61 would cause a deadlock (semaphore would get into a state where
24 it was available but waiters were still blocked). 62 it was available but waiters were still blocked).
25 - calling throw on a coroutine that is waiting for a semaphore will 63 - calling throw on a coroutine that is waiting for a semaphore will

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines