1 | Revision history for Perl extension EV |
1 | Revision history for Perl extension EV |
2 | |
2 | |
3 | Changes marked with (libev) are changes in libev, and have more |
3 | Changes marked with (libev) are changes in libev, and have more |
4 | documentation in the libev Changes file. |
4 | documentation in the libev Changes file. |
5 | |
5 | |
|
|
6 | - EV::run now returns boolean. |
|
|
7 | - API version 5:1. |
|
|
8 | - document that cleanup watchers are not availble via perl. |
|
|
9 | |
|
|
10 | 4.11 Sat Feb 4 19:56:26 CET 2012 |
|
|
11 | - (libev) implement memory fences for (obsolete) llvm-gcc. |
|
|
12 | |
|
|
13 | 4.10 Thu Jan 19 18:54:23 CET 2012 |
|
|
14 | - (libev) fix a race where the workaround against the epoll fork |
|
|
15 | bugs caused signals to not be handled anymore. |
|
|
16 | - (libev) correct backend_fudge for most backends, and implement |
|
|
17 | a windows specific workaround to avoid looping because we call |
|
|
18 | both select and Sleep, both with different time resolutions. |
|
|
19 | - e_new wasn't declared static (causing very minor .so bloat). |
|
|
20 | - replace more old api names by new ones. |
|
|
21 | |
|
|
22 | 4.03 Tue Jan 11 14:51:05 CET 2011 |
6 | - do not avoid the clock_gettime call on GNU/Linux anymore, as EV |
23 | - do not avoid the clock_gettime call on GNU/Linux anymore, as EV |
7 | links against -lpthread anyways - as a result, EV might now take |
24 | links against -lpthread anyways - as a result, EV might now take |
8 | advantage of fast userspace clock_gettime implementations, |
25 | advantage of fast userspace clock_gettime implementations, |
9 | but also links against -lrt. |
26 | but also links against -lrt. |
|
|
27 | - (libev) lots of event port bug workarounds. |
|
|
28 | - (libev) officially support files in I/O watchers. |
|
|
29 | - (libev) new function ev_feed_signal. |
|
|
30 | - fix documentation parts still refering to the 3.x API. |
10 | |
31 | |
11 | 4.02 Thu Dec 30 08:27:41 CET 2010 |
32 | 4.02 Thu Dec 30 08:27:41 CET 2010 |
12 | - the revents argument did not stringify correctly, as only the |
33 | - the revents argument did not stringify correctly, as only the |
13 | numeric value was updated, while the string value was kept from |
34 | numeric value was updated, while the string value was kept from |
14 | previous invocations. |
35 | previous invocations. |