| 1 | Revision history for Perl extension Coro. |
1 | Revision history for Perl extension Coro. |
|
|
2 | |
|
|
3 | 0.1 Tue Jul 24 01:47:53 CEST 2001 |
|
|
4 | - release candidate 3. A rather new internal structure :( |
|
|
5 | - the great renaming: Damian Conway gave me a suitable replacement |
|
|
6 | for yield. |
|
|
7 | - added Coro/libcoro, a portable coroutine implementation for C |
|
|
8 | (not even perl-dependent!!!), which can be used by Coro::State. |
|
|
9 | - renamed SAVE_DEFSV (on xs-level only) to avoid symbol clash in |
|
|
10 | perl-5.6. |
|
|
11 | - new function Coro::Event::idle. |
|
|
12 | - the idle process is now overriden |
|
|
13 | by default in Coro::Event. |
|
|
14 | - Coro::Channel now enforces the size. |
|
|
15 | - canceling events now works in all cases. |
|
|
16 | - Coro state now include $_ and $@. |
|
|
17 | - yet another bug workaround that I do not really understand :( |
|
|
18 | - new module Coro::Event::IO (very undocumented) to do |
|
|
19 | non-blocking i/o. |
|
|
20 | - performance tuning. |
|
|
21 | |
|
|
22 | 0.08 Thu Jul 19 06:13:25 CEST 2001 |
|
|
23 | - release candidate 2 (new functionality). |
|
|
24 | - add Coro::State::flush function. |
|
|
25 | - transfer now supports a flags value (mostly for speed ATM). |
|
|
26 | - might compile and work in the presence of threads now. |
|
|
27 | - continuations have a saner syntax. |
|
|
28 | - no more memleaks. |
|
|
29 | |
|
|
30 | 0.07 Tue Jul 17 17:40:18 CEST 2001 |
|
|
31 | - release candidate 1 ;) |
|
|
32 | - slightly nicer code. |
|
|
33 | - fixed a scheduling bug in Coro::Event. |
| 2 | |
34 | |
| 3 | 0.06 Tue Jul 17 04:23:24 CEST 2001 |
35 | 0.06 Tue Jul 17 04:23:24 CEST 2001 |
| 4 | - ok, I found the showstopper - the same sub must not be |
36 | - ok, I found the showstopper - the same sub must not be |
| 5 | re-entered in two different coroutines, otherwise => crash. I |
37 | re-entered in two different coroutines, otherwise => crash. I |
| 6 | see no easy solution to this problem, except by walking the call |
38 | see no easy solution to this problem, except by walking the call |
