… | |
… | |
11 | |
11 | |
12 | 5.0 |
12 | 5.0 |
13 | - NEW ARCHITECTURE: use the latest 4.x version if you experience |
13 | - NEW ARCHITECTURE: use the latest 4.x version if you experience |
14 | stability issues. |
14 | stability issues. |
15 | - bump API version to 7 - all dependents must be recompiled. |
15 | - bump API version to 7 - all dependents must be recompiled. |
16 | - removed timed_down and timed_guard functions - they were not being |
16 | - removed timed_* functions - they were not being used anyways |
17 | used anyways and should be replaced by a more generic mechanism - |
17 | and should be replaced by a more generic mechanism - |
18 | and were annoying to support anyways :) |
18 | and were annoying to support anyways :) |
19 | - removed SemaphoreSet's waiter method - use sem instead. |
19 | - removed SemaphoreSet's waiter method - use sem instead. |
20 | - Coro::Semaphore->adjust didn't correctly wake up enough waiters. |
20 | - Coro::Semaphore->adjust didn't correctly wake up enough waiters. |
21 | - async_pool did free a scalar value twice |
21 | - async_pool did free a scalar value twice |
22 | ("Attempt to unreference..."). |
22 | ("Attempt to unreference..."). |
23 | - fix a longstanding bug where calling terminate on a coro that |
23 | - fix a longstanding bug where calling terminate on a coro that |
24 | was waiting for a semaphore that was just becoming available |
24 | was waiting for a semaphore that was just becoming available |
25 | would cause a deadlock (semaphore would get into a state where |
25 | would cause a deadlock (semaphore would get into a state where |
26 | it was available but waiters were waiting(. |
26 | it was available but waiters were still blocked). |
|
|
27 | - calling throw on a coroutine that is waiting for a semaphore will |
|
|
28 | no longer make it acquire the semaphore (and thus leak a count). |
27 | - perl's process emulation is now not even theoretically supported |
29 | - perl's process emulation is now not even theoretically supported |
28 | anymore. |
30 | anymore. |
|
|
31 | - new function Coro::Semaphore::wait. |
29 | - use named constants in Coro::Channel (Richard Hundt). |
32 | - use named constants in Coro::Channel (Richard Hundt). |
30 | - directly patch the entersub opcode calling SLF functions (cede, |
33 | - directly patch the entersub opcode calling SLF functions (cede, |
31 | transfer and so on). this does speed up context switching, but |
34 | transfer and so on). this does speed up context switching, but |
32 | more importanly, it frees us from the hardcoded behaviour of |
35 | more importanly, it frees us from the hardcoded behaviour of |
33 | entersub, so we might actually be able to return something from |
36 | entersub, so we might actually be able to return something from |
… | |
… | |
44 | - used new SLF interface to speed up Coro::AIO by roughly a factor of |
47 | - used new SLF interface to speed up Coro::AIO by roughly a factor of |
45 | four and reduce its memory usage considerably. |
48 | four and reduce its memory usage considerably. |
46 | - implement Coro::SemaphoreSet purely in terms of Coro::Semaphore, |
49 | - implement Coro::SemaphoreSet purely in terms of Coro::Semaphore, |
47 | for a nice speedup and vastly more correct behaviour. Also implement |
50 | for a nice speedup and vastly more correct behaviour. Also implement |
48 | a new method "sem" to get at the underlying semaphore object. |
51 | a new method "sem" to get at the underlying semaphore object. |
|
|
52 | - implement Coro::Channel in terms of Coro::Semaphore, for a moderate |
|
|
53 | (in comparison) 20-40% speedup. |
|
|
54 | - used new SLF interface to reimplement Coro::Signal gaining |
|
|
55 | some unknown (because I was too lazy), but certain, speedup, and also |
|
|
56 | making signals reliable for the first time. |
49 | - forgot to include Coro/libcoro/README in the dist for all these years. |
57 | - forgot to include Coro/libcoro/README in the dist for all these years. |
50 | - work around a freebsd pthreads bug (manual testcancel is required as |
58 | - work around a freebsd pthreads bug (manual testcancel is required as |
51 | pthread_cond_wait isn't a cancellation point on freebsd). |
59 | pthread_cond_wait isn't a cancellation point on freebsd). |
52 | |
60 | |
53 | 4.913 Sat Nov 15 07:58:28 CET 2008 |
61 | 4.913 Sat Nov 15 07:58:28 CET 2008 |