| 1 | Revision history for Perl extension Coro. |
1 | Revision history for Perl extension Coro. |
|
|
2 | |
|
|
3 | 1.31 Tue Aug 30 23:31:33 CEST 2005 |
|
|
4 | - some portability fixes/workarounds. |
|
|
5 | |
|
|
6 | 1.3 Sat Aug 20 03:08:56 CEST 2005 |
|
|
7 | - no code changes. module seems to work fine. |
|
|
8 | - improve Coro::State docs, remove reference to nonexisting |
|
|
9 | Coro::State::flush method. |
|
|
10 | - no longer autodetect windows, present it as an option instead. |
|
|
11 | |
|
|
12 | 1.2 Mon May 16 02:00:55 CEST 2005 |
|
|
13 | - included libcoro.c earlier in State.xs, might improve portability. |
|
|
14 | - use a faster and possibly more stable Coro::Cont implementation. |
|
|
15 | - accept x86_64 in addition to amd64 for optimized linux-amd64 support. |
|
|
16 | - fix bugs Coro::SemaphoreSet that could cause locks never to be freed. |
|
|
17 | - fix bugs in CoroAPI.h and document it in Coro::MakeMaker. |
|
|
18 | |
|
|
19 | 1.11 Thu Mar 3 18:00:52 CET 2005 |
|
|
20 | - change of contact address. |
|
|
21 | |
|
|
22 | 1.1 Tue Feb 22 20:51:16 CET 2005 |
|
|
23 | - support [l]inux method on amd64. |
|
|
24 | - allow some context switches while compiling/eval'ing. |
|
|
25 | |
|
|
26 | 1.0 Tue Aug 10 03:47:27 CEST 2004 |
|
|
27 | - Event 0.89 fixes the bug again. |
|
|
28 | - fix the remaining(??) memleak. I didn't free the cache-AV for |
|
|
29 | padlists, so one AV per created anon-sub leaked. |
| 2 | |
30 | |
| 3 | 0.97 Fri May 14 15:23:32 CEST 2004 |
31 | 0.97 Fri May 14 15:23:32 CEST 2004 |
| 4 | - remove stupid gcc extension that was an experiment only anyway. |
32 | - remove stupid gcc extension that was an experiment only anyway. |
| 5 | |
33 | |
| 6 | 0.96 Thu May 13 18:09:29 CEST 2004 |
34 | 0.96 Thu May 13 18:09:29 CEST 2004 |
| 7 | - tell people if they have yet anothe rbroken Event variant. |
35 | - tell people if they have yet another broken Event variant. |
| 8 | - made Coro to work _better_ with threads (it seems that, as long |
36 | - made Coro to work _better_ with threads (it seems that, as long |
| 9 | as you use Coros in one thread only everything will work fine. |
37 | as you use Coros in one thread only everything will work fine. |
| 10 | Looking at the perl source the problem might be missing locking |
38 | Looking at the perl source the problem might be missing locking |
| 11 | between Coro and some perl internal routines. That's not easily |
39 | between Coro and some perl internal routines. That's not easily |
| 12 | fixable). |
40 | fixable). |
