| … | |
… | |
| 6 | but very lacking in others (higher level ipc)). |
6 | but very lacking in others (higher level ipc)). |
| 7 | TODO: unready_all |
7 | TODO: unready_all |
| 8 | TODO: myhttpd header parsing |
8 | TODO: myhttpd header parsing |
| 9 | TODO: channel->maxsize(newsize)? |
9 | TODO: channel->maxsize(newsize)? |
| 10 | |
10 | |
|
|
11 | - convert Coro::Util into a "perl compatibility wrapper" - the functions |
|
|
12 | are less useful now, but are drop-in replacements for existing |
|
|
13 | functions, listing better alternatives in the documentation. This also |
|
|
14 | fixes a bug in Coro::LWP which naively substituted Socket::inet_aton |
|
|
15 | with Coro::Util::inet_aton. |
|
|
16 | - fix Coro::Util::gethost* functions. |
|
|
17 | |
|
|
18 | 5.21 Wed Dec 16 07:19:51 CET 2009 |
|
|
19 | - automatically load Coro::AnyEvent when AnyEvent and Coro are used |
|
|
20 | together. |
|
|
21 | - add some examples on how to combine other event loops with Coro in |
|
|
22 | Coro::AnyEvent, and how to run it (and not to block). Seems to be |
|
|
23 | the most common source of confusion. |
|
|
24 | - try to catch people naively blocking in an event callback. |
|
|
25 | - work around the perl filehandle bug issue in conjunction with |
|
|
26 | older common::sense (as indirectly pointed out by ZSystem). |
|
|
27 | - clarify the "not from signal handlers" section. |
|
|
28 | |
|
|
29 | 5.2 Sun Oct 4 14:54:24 CEST 2009 |
| 11 | - Coro::Storable destroyed the prototypes of the functions it wrapped. |
30 | - Coro::Storable destroyed the prototypes of the functions it wrapped. |
|
|
31 | - export rouse_cb and rouse_wait by default now. |
| 12 | - fix various prototype mismatches in Coro::AnyEvent and Coro::Handle. |
32 | - fix various prototype mismatches in Coro::AnyEvent and Coro::Handle. |
|
|
33 | - new method $state->swap_sv. |
| 13 | - added section on "windows process emulation" to the manpage, |
34 | - added section on "windows process emulation" to the manpage, |
| 14 | after a not-so-fruitful (nor-friendly) "discussion" with chip |
35 | after a not-so-fruitful (nor-friendly) "discussion" with chip |
| 15 | salzenberg (discussion implies arguments, but his only arguments |
36 | salzenberg (discussion implies arguments, but his only arguments |
| 16 | were ad-hominems, one wonders why he started it in the first |
37 | 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, |
38 | place). I hope this explains it well enough for him to understand, |
