| 1 | Revision history for Perl extension Coro. |
1 | Revision history for Perl extension Coro. |
| 2 | |
2 | |
|
|
3 | - included libcoro.c earlier in State.xs, might improve portability. |
|
|
4 | - use a faster and possibly more stable Coro::Cont implementation. |
|
|
5 | - accept x86_64 in addition to amd64 for optimized linux-amd64 support. |
|
|
6 | |
|
|
7 | 1.11 Thu Mar 3 18:00:52 CET 2005 |
|
|
8 | - change of contact address. |
|
|
9 | |
|
|
10 | 1.1 Tue Feb 22 20:51:16 CET 2005 |
|
|
11 | - support [l]inux method on amd64. |
|
|
12 | - make some context switches while compiling/eval'ing work. |
|
|
13 | |
|
|
14 | 1.0 Tue Aug 10 03:47:27 CEST 2004 |
|
|
15 | - Event 0.89 fixes the bug again. |
|
|
16 | - fix the remaining(??) memleak. I didn't free the cache-AV for |
|
|
17 | padlists, so one AV per created anon-sub leaked. |
|
|
18 | |
|
|
19 | 0.97 Fri May 14 15:23:32 CEST 2004 |
|
|
20 | - remove stupid gcc extension that was an experiment only anyway. |
|
|
21 | |
|
|
22 | 0.96 Thu May 13 18:09:29 CEST 2004 |
|
|
23 | - tell people if they have yet another broken Event variant. |
| 3 | - made Coro to work _better_ with threads (it seems that, as long |
24 | - made Coro to work _better_ with threads (it seems that, as long |
| 4 | as you use Coros in one thread only everything will work fine. |
25 | as you use Coros in one thread only everything will work fine. |
| 5 | Looking at the perl source the problem might be missing locking |
26 | Looking at the perl source the problem might be missing locking |
| 6 | between Coro and some perl internal routines. That's not easily |
27 | between Coro and some perl internal routines. That's not easily |
| 7 | fixable). |
28 | fixable). |
|
|
29 | - (hopefully) got rid of the static xnext inside transfer. |
| 8 | |
30 | |
| 9 | 0.95 Sun Feb 15 03:20:28 CET 2004 |
31 | 0.95 Sun Feb 15 03:20:28 CET 2004 |
| 10 | - removed Coro::State::flush, implemented a new and much |
32 | - removed Coro::State::flush, implemented a new and much |
| 11 | faster caching mechanism by attaching magic to the CV. |
33 | faster caching mechanism by attaching magic to the CV. |
| 12 | - a memleak with (real) closures remains. |
34 | - a memleak with (real) closures remains. |
