| 1 | Revision history for Perl extension AnyEvent. |
1 | Revision history for Perl extension AnyEvent. |
| 2 | |
2 | |
|
|
3 | - fix a bug in the pure perl backend that kept watchers alive |
|
|
4 | when multiple watchers were registered for the same fh/poll combo. |
|
|
5 | - add a benchmark section showing AnyEvent overhead and comparing |
|
|
6 | the different event loops with each other. |
|
|
7 | - make Qt and Event::Lib support non-experimental. |
|
|
8 | - support POE as "backend" (with some caveats, POE is not generic |
|
|
9 | enough, and darn slow). |
|
|
10 | - support Wx and Prima through POE. |
|
|
11 | - optimise perl backend a bit (less memory). |
|
|
12 | |
|
|
13 | 3.2 Thu Apr 24 10:10:40 CEST 2008 |
|
|
14 | - do not die when anyevent watchers are destroyed while running callbacks |
|
|
15 | in the pureperl backend (could only happen when two watchers are registered |
|
|
16 | for the same fh/poll combo). |
|
|
17 | - support autoloading for child watchers, was broken in all versions. |
| 3 | - implement PERL_ANYEVENT_MODEL env variable. |
18 | - implement PERL_ANYEVENT_MODEL env variable. |
| 4 | - implement interface to the (very crashy/buggy) Event::Lib module. |
19 | - (experimental) implement interface to the (very crashy/buggy) Event::Lib module. |
| 5 | - tried to implement an interface to Qt, but perl-Qt is in a |
20 | - (experimental) implement interface to the Qt module (cannot be autoprobed). |
| 6 | totally broken state (Qt::app returns an invalid object, memory |
21 | - this release is IO:AnyEvent-proof. |
| 7 | corruption ensues etc.) |
|
|
| 8 | |
22 | |
| 9 | 3.12 Tue Apr 22 07:11:46 CEST 2008 |
23 | 3.12 Tue Apr 22 07:11:46 CEST 2008 |
| 10 | - reinstate AUTHOR section that got lost somehow. |
24 | - reinstate AUTHOR section that got lost somehow. |
| 11 | - do not hang in the testsuite with badly broken perls (activestate, |
25 | - do not hang in the testsuite with badly broken perls (activestate, |
| 12 | strawberry...), but instead diagnose the problem and continue. |
26 | strawberry...), but instead diagnose the problem and continue. |
