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.493 by root, Wed Jun 17 03:45:34 2009 UTC

2 2
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)).
7TODO: unready_all
8TODO: myhttpd header parsing
7 9
85.0 10 - speed up ready queue management/context switching by using a linked
11 list instead of an array (~5-10%).
12 - implement "watch" command in Coro::Debug shells.
13
145.132 Fri May 29 09:00:39 CEST 2009
15 - do not keep a reference to the argument itself in
16 Coro::Semaphore::guard, as it could change later.
17 - support SO_RCVBUF/SO_SNDBUF nonstandard Coro::Socket options,
18 should support a prepare callback.
19
205.131 Mon Mar 16 23:20:37 CET 2009
21 - implement and document Coro->suspend, Coro->resume.
22 - fix Coro::Select implementation to not (often) close
23 the passed file descriptors (testcase provided by pippijn).
24
255.13 Mon Dec 15 21:51:42 CET 2008
26 - EXPERIMENTAL: implement dynamic winds (on_enter/on_leave).
27 - don't set diehook to C<undef> but instead to NULL, to avoid
28 spurious warnings.
29 - fix a lot of bugs in Coro::SemaphoreSet.
30 - Coro::SemaphoreSet will less often create a semaphore needlessly.
31 - add Coro::SemaphoreSet::count and wait methods.
32 - take advantage of the new Guard module.
33 - deprecate Coro::guard.
34 - try to fix the dreaded 01_unblock tests once more. I hate it when
35 testsuites need more fixing than the code they are supposed to test.
36 - croak in more cases when a required callback isn't resolvable.
37 - fix some minor issues in Coro::State->call/eval.
38 - use current coroutine context instead of a temporary one
39 when temporarily switching to another coroutine.
40 - do not call C-level on_destroy handlers during global destruction,
41 to avoid needless segfaults.
42
435.12 Sun Dec 7 13:30:38 CET 2008
44 - add default config for MirOS, which seems to be a bug-to-bug
45 compatible fork of openbsd ("world domination by releasing
46 openbsd cvs before the openbsd folks do it" or so :).
47 - free_padlist did destroy the names pad, not good, but didn't
48 seem to bother perl - this could fix issues such as eval ""
49 inside a function called from multiple coroutines.
50 - use a different method to detect destruction time.
51 - be more careful when freeing padlists just before global
52 destruction.
53 - fixed and expanded the call/cc example.
54 - renamed _terminate to _coro_run.
55 - new method Coro::Channel->shutdown.
56 - try pthreads on openbsd <4.4 (broken sigaltstack, will
57 pthreads fare better?).
58 - be less picky about destroying "a" running coroutine.
59
605.11 Tue Nov 25 21:49:05 CET 2008
61 - DEBUGGING in 5.10.0 is a mess: it constantly flags perfectly
62 working code with failed assertions, introducing more bugs than
63 it fixes, requiring elaborate workarounds :(
64
655.1 Mon Nov 24 08:54:59 CET 2008
66 - wrote a small introductory tutorial - Coro::Intro.
67 - convert Coro::Timer, Coro::Select and Coro::Util to rouse API.
68 - Coro::Select did errornously dup the file descriptors
69 and didn't work with all AnyEvent backends.
70 - Coro::Select wasn't imported correctly form Coro::LWP, causing blocking
71 LWP data transfers.
72 - disassociate c contexts from coro objects - this is agruably more
73 correct, but mostly allows sharing of cctxs between coro and state
74 objects, for added memory savings and speed increases.
75 - bumped $Coro::POOL_RSS up to 32kb by default.
76 - no longer set the optype to OP_CUSTOM, as B::* understandably
77 doesn't like this very much (and we *are* a type of entersub).
78 - implement state cloning, just to prove that call/cc can be done.
79 - automatically load Coro::AnyEvent in Coro::Handle.
80 - wrap ->cancel calls in eval inside Coro::Handle as EV watchers
81 do not have this method (and don't need it either).
82 - speed up generic anyevent methods in Coro::Handle by using rouse
83 callbacks.
84 - allow coroutines in $Coro::IDLE, speeding up Coro::AnyEvent and
85 others. It also makes the debugger happier, as you can trace
86 through the idle threads now.
87 - add comppad_name* and hints ($^H, %^H) to per-thread variables.
88 - eg/event was pretty broken.
89 - better 5.8.6 compatibility.
90
915.0 Thu Nov 20 10:35:05 CET 2008
9 - NEW ARCHITECTURE: use the latest 4.x version if you experience 92 - NEW ARCHITECTURE: use the latest 4.x version if you experience
10 stability issues. 93 stability issues.
11 - bump API version to 7 - all dependents must be recompiled. 94 - bump API version to 7 - all dependents must be recompiled.
12 - removed timed_* functions - they were not being used anyways 95 - removed timed_* functions - they were not being used anyways
13 and should be replaced by a more generic mechanism - 96 and should be replaced by a more generic mechanism -
14 and were annoying to support anyways :) 97 and were annoying to support anyways :)
15 - removed SemaphoreSet's waiter method - use sem instead. 98 - removed SemaphoreSet's waiter method - use sem method instead.
16 - Coro::Semaphore->adjust didn't correctly wake up enough waiters. 99 - Coro::Semaphore->adjust didn't correctly wake up enough waiters.
17 - async_pool did free a scalar value twice 100 - async_pool did free a scalar value twice
18 ("Attempt to unreference..."). 101 ("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 102 - fix a longstanding bug where calling terminate on a coro that
22 was waiting for a semaphore that was just becoming available 103 was waiting for a semaphore that was just becoming available
23 would cause a deadlock (semaphore would get into a state where 104 would cause a deadlock (semaphore would get into a state where
24 it was available but waiters were still blocked). 105 it was available but waiters were still blocked).
25 - calling throw on a coroutine that is waiting for a semaphore will 106 - calling throw on a coroutine that is waiting for a semaphore will

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines