| 1 | Revision history for Perl extension AnyEvent. |
1 | Revision history for Perl extension AnyEvent. |
| 2 | |
2 | |
| 3 | TODO: document TCP_*** constants |
3 | TODO: document TCP_*** constants |
| 4 | |
|
|
| 5 | TODO: AE::logger |
|
|
| 6 | TODO: add debug/trace logging to some modules |
4 | TODO: add debug/trace logging to some modules |
|
|
5 | TODO: AnyEvent::IO |
|
|
6 | |
|
|
7 | - documented Rocco fabricating statements about AnyEvent and me. |
|
|
8 | - the default logging level was not properly documented in a variety of |
|
|
9 | places, this has hopefully been rectified. |
|
|
10 | - updated uts46data.pl for unicode 6.1.0. |
|
|
11 | - made log messages genearted by AnyEvent submodules not |
|
|
12 | include the package name anymore, as it will be logged |
|
|
13 | by default already. |
|
|
14 | - upgrade to the trick used by common-sense 3.5 to work |
|
|
15 | around extra warning torture/breakage under perl 5.15.x. |
|
|
16 | |
|
|
17 | 6.14 Tue Jan 31 20:00:24 CET 2012 |
|
|
18 | - AnyEvent::Impl::Tk was broken due to a mysterious "die" inside, |
|
|
19 | probably an editing mistake (reported by Darin McBride). |
|
|
20 | |
|
|
21 | 6.13 Thu Jan 12 07:27:01 CET 2012 |
|
|
22 | - AnyEvent::Util::fork_call checked for POSIX availability in the wrong way, |
|
|
23 | causing it to fail if POSIX wasn't loaded already (analysed by Rock Power). |
|
|
24 | - AnyEvent::Handle::push_read (line => did pass $1 directly, so |
|
|
25 | regex-matching inside the callback would change the parameter, despite |
|
|
26 | $1 being dynamically scoped per-block. this perl bug is now being |
|
|
27 | worked around (testcase by Cindy Wang). |
|
|
28 | |
|
|
29 | 6.12 Mon Dec 12 13:21:10 CET 2011 |
|
|
30 | - $! was clobbered by subsequent calls in tcp_connect, due to |
|
|
31 | the postpone not saving/restoring it (analyzed by Richard Garnish). |
|
|
32 | |
|
|
33 | 6.11 Tue Nov 22 10:36:05 CET 2011 |
|
|
34 | - Tk cannot create windows when tainted unless you set a title, so |
|
|
35 | set a dummy title for AnyEvent's dummy mainwindow. How dummy. |
|
|
36 | - escape any nonprintable/nonascii characters when stringifying |
|
|
37 | backtraces. |
|
|
38 | - log the reason loading an interface module fails to load at level debug. |
|
|
39 | |
|
|
40 | 6.1 Tue Oct 4 19:44:30 CEST 2011 |
| 7 | - INCOMPATIBLE CHANGE: the default log level is now "4" (error |
41 | - INCOMPATIBLE CHANGE: the default log level is now "4" (error |
| 8 | and above), and some messages inside AnyEvent have been elevated |
42 | and above), and some messages inside AnyEvent have been elevated |
| 9 | to higher log levels to print by default. |
43 | to higher log levels to print by default. |
| 10 | - AnyEvent::log, unlike AnyEvent::Log::log, did not always exit on fatal. |
44 | - AnyEvent::log, unlike AnyEvent::Log::log, did not always exit on fatal. |
| 11 | - work around yet another signal race bug, newly introduced by POE. My |
45 | - work around yet another signal race bug, newly introduced by POE. My |
| … | |
… | |
| 24 | delivery. |
58 | delivery. |
| 25 | - mention some debugging aids in the tutorial. |
59 | - mention some debugging aids in the tutorial. |
| 26 | - new env variable PERL_ANYEVENT_MAX_SIGNAL_LATENCY. |
60 | - new env variable PERL_ANYEVENT_MAX_SIGNAL_LATENCY. |
| 27 | - private (%namespace) log contexts in PERL_ANYEVENT_LOG now have the name |
61 | - private (%namespace) log contexts in PERL_ANYEVENT_LOG now have the name |
| 28 | of the context as title. |
62 | of the context as title. |
|
|
63 | - AnyEvent::Strict would not restore read-write access to $_ when a callback |
|
|
64 | died - this is a user bug, but since AE::Strict exists to help dbeugging... |
| 29 | - detect the extremely evil IO::Async::Loop::AnyEvent module and refuse |
65 | - detect the extremely evil IO::Async::Loop::AnyEvent module and refuse |
| 30 | to work with it - the author is well aware of the issues but refuses |
66 | to work with it - the author is well aware of the issues but refuses |
| 31 | to fix them. This extreme step has been taken because the module actively |
67 | to fix them. This extreme step has been taken because the module actively |
| 32 | attacks the goals of AnyEvent and makes it harder for module authors to use |
68 | attacks the goals of AnyEvent and makes it harder for module authors to use |
| 33 | AnyEvent. |
69 | AnyEvent. |
