| 1 | Revision history for Perl extension AnyEvent. |
1 | Revision history for Perl extension AnyEvent. |
|
|
2 | |
|
|
3 | TODO: - implemented idle watchers, where applicable. |
|
|
4 | - AnyEvent->time died when Event backend was in use. |
|
|
5 | - fix a memleak in the Tk backend. |
|
|
6 | - sped up Tk timer handling. |
|
|
7 | - clip negative "after" values to 0 in AnyEvent::Impl::Event |
|
|
8 | to avoid spamming out warning messages. |
|
|
9 | - fix Qt timers without interval. |
|
|
10 | - avoid Qt zero-timeout specialcase, in old libqt's. |
|
|
11 | |
|
|
12 | 4.352 Mon Apr 20 16:31:11 CEST 2009 |
|
|
13 | - fix AnyEvent::Strict error messages for child watchers. |
|
|
14 | - fix/update Makefile.PL "recommends" versions. |
|
|
15 | - add AnyEvent->now_update. |
|
|
16 | |
|
|
17 | 4.351 Sat Apr 11 07:56:14 CEST 2009 |
|
|
18 | - actually make the signal pipe work under win32. |
|
|
19 | - localise $! in signal handler to avoid changing $!, although |
|
|
20 | perl itself does not seem to save/restore errno either. |
|
|
21 | - set the cloexec flag on the signal pipe (normally set by perl too). |
|
|
22 | |
|
|
23 | 4.35 Fri Mar 27 11:48:20 CET 2009 |
|
|
24 | - event models relying on AnyEvent's signal watcher emulation did |
|
|
25 | invoke the callback asynchronously, contradicting documentation |
|
|
26 | and causing signals to get lost (this includes AnyEvent's own |
|
|
27 | event loop). AnyEvent now uses the standard pipe trick to make |
|
|
28 | callback execution synchronous to the event loop. |
|
|
29 | - AnyEvent::Handle didn't free TLS context data on DESTROY |
|
|
30 | (patch by Pavel Shaydo). |
|
|
31 | - work around the ever-incompatibly-changing API of MakeMaker. |
|
|
32 | - document that changing global variables without restoring them |
|
|
33 | is a bad idea in Perl (noted by Adam Rosenstein). |
|
|
34 | - AnyEvent::Strict now barfs if ->io is passed a file. |
| 2 | |
35 | |
| 3 | 4.34 Thu Feb 12 18:32:45 CET 2009 |
36 | 4.34 Thu Feb 12 18:32:45 CET 2009 |
| 4 | - separately buffer TLS read data, as otherwise the read queue could |
37 | - separately buffer TLS read data, as otherwise the read queue could |
| 5 | deadlock as receiving data is not expected while draining the |
38 | deadlock as receiving data is not expected while draining the |
| 6 | read queue (which cna only happen with TLS). |
39 | read queue (which cna only happen with TLS). |
