| 1 | Revision history for Perl extension Coro. |
1 | Revision history for Perl extension Coro. |
| 2 | |
2 | |
| 3 | TODO: should explore PerlIO::coroaio (perl leaks like hell). |
3 | TODO: should explore PerlIO::coroaio (perl leaks like hell). |
| 4 | TODO: maybe implement a default message channel, very much like Erlang's |
|
|
| 5 | actor model (which is cool in a lot of important aspects (failures!), |
|
|
| 6 | but very lacking in others (higher level ipc)). |
|
|
| 7 | TODO: unready_all |
4 | TODO: unready_all |
| 8 | TODO: myhttpd header parsing |
5 | TODO: myhttpd header parsing |
| 9 | TODO: channel->maxsize(newsize)? |
6 | TODO: channel->maxsize(newsize)? |
|
|
7 | TODO: http://www.microsoft.com/msj/archive/s2ce.aspx |
| 10 | |
8 | |
|
|
9 | 5.25 Thu Nov 11 01:08:39 CET 2010 |
|
|
10 | - try a different approach on netbsd - netbsd 5 finally has marginally |
|
|
11 | working pthreads, but still broken ucontext/sigaltstack. |
|
|
12 | - openbsd 4.8 finally got their act together, Coro works out of the box |
|
|
13 | with asm, setjmp and pthreads (no change, just informational). |
|
|
14 | |
|
|
15 | 5.24 Sat Oct 23 11:27:12 CEST 2010 |
|
|
16 | - port to the EV 4.0 API. |
|
|
17 | - work around bugs in mingw32, making strawberry perl work |
|
|
18 | out of the box. |
|
|
19 | - correctly modify Coro::AIO function prototypes |
|
|
20 | so that they reflect the "no optional parameters" rule. |
|
|
21 | - "ported" libcoro to C++. |
|
|
22 | |
|
|
23 | 5.23 Mon May 17 18:50:42 CEST 2010 |
|
|
24 | - be more resistant to ordering changes when initialising |
|
|
25 | Coro::AnyEvent, Coro::EV and Coro::Event (reported by Matthias |
|
|
26 | Waldorf). |
|
|
27 | - document that perl 5.12 deliberately removed support for cloning. |
|
|
28 | |
|
|
29 | 5.22 Wed Apr 14 03:55:35 CEST 2010 |
|
|
30 | - correctly return udnef on errors in Coro::Handle::read/write |
|
|
31 | (testcase by Marc Mims). |
|
|
32 | - convert Coro::Util into a "perl compatibility wrapper" - the functions |
|
|
33 | are less useful now, but are drop-in replacements for existing |
|
|
34 | functions, listing better alternatives in the documentation. This also |
|
|
35 | fixes a bug in Coro::LWP which naively substituted Socket::inet_aton |
|
|
36 | with Coro::Util::inet_aton. |
|
|
37 | - do not override $Coro::idle unconditionally in Coro.pm, as other |
|
|
38 | modules could have provided their own idle coro already |
|
|
39 | (for exmaple, Coro::AnyEvent). |
|
|
40 | - fix Coro::Util::gethost* functions. |
|
|
41 | - Coro::Timer corretcly exports it's symbols (reported by Hideki Yamamura). |
|
|
42 | |
|
|
43 | 5.21 Wed Dec 16 07:19:51 CET 2009 |
|
|
44 | - automatically load Coro::AnyEvent when AnyEvent and Coro are used |
|
|
45 | together. |
|
|
46 | - add some examples on how to combine other event loops with Coro in |
|
|
47 | Coro::AnyEvent, and how to run it (and not to block). Seems to be |
|
|
48 | the most common source of confusion. |
|
|
49 | - try to catch people naively blocking in an event callback. |
|
|
50 | - work around the perl filehandle bug issue in conjunction with |
|
|
51 | older common::sense (as indirectly pointed out by ZSystem). |
|
|
52 | - clarify the "not from signal handlers" section. |
|
|
53 | |
|
|
54 | 5.2 Sun Oct 4 14:54:24 CEST 2009 |
| 11 | - Coro::Storable destroyed the prototypes of the functions it wrapped. |
55 | - Coro::Storable destroyed the prototypes of the functions it wrapped. |
|
|
56 | - export rouse_cb and rouse_wait by default now. |
| 12 | - fix various prototype mismatches in Coro::AnyEvent and Coro::Handle. |
57 | - fix various prototype mismatches in Coro::AnyEvent and Coro::Handle. |
|
|
58 | - new method $state->swap_sv. |
| 13 | - added section on "windows process emulation" to the manpage, |
59 | - added section on "windows process emulation" to the manpage, |
| 14 | after a not-so-fruitful (nor-friendly) "discussion" with chip |
60 | after a not-so-fruitful (nor-friendly) "discussion" with chip |
| 15 | salzenberg (discussion implies arguments, but his only arguments |
61 | salzenberg (discussion implies arguments, but his only arguments |
| 16 | were ad-hominems, one wonders why he started it in the first |
62 | were ad-hominems, one wonders why he started it in the first |
| 17 | place). I hope this explains it well enough for him to understand, |
63 | place). I hope this explains it well enough for him to understand, |
