| 1 | Revision history for libev, a high-performance and full-featured event loop. |
1 | Revision history for libev, a high-performance and full-featured event loop. |
|
|
2 | |
|
|
3 | TODO: ev_time_freeze, ev_time_thaw |
|
|
4 | TODO: ev_walk |
|
|
5 | TODO: ev_stop_all |
|
|
6 | TODO: fix signal handling(?) under win32 |
|
|
7 | 3.54 |
|
|
8 | - do not leave the event loop early just because we have no active |
|
|
9 | watchers, fixing a problem when embedding a kqueue loop |
|
|
10 | that has active kernel events but no registered watchers |
|
|
11 | (reported by blacksand blacksand). |
|
|
12 | - correctly zero the idx values for arrays, so destroying and |
|
|
13 | reinitialising the default loop actually works (patch by |
|
|
14 | Malek Hadj-Ali). |
|
|
15 | - new EV_CUSTOM revents flag for use by applications. |
|
|
16 | |
|
|
17 | 3.53 Sun Feb 15 02:38:20 CET 2009 |
|
|
18 | - fix a bug in event pipe creation on win32 that would cause a |
|
|
19 | failed assertion on event loop creation (patch by Malek Hadj-Ali). |
|
|
20 | - probe for CLOCK_REALTIME support at runtime as well and fall |
|
|
21 | back to gettimeofday if there is an error, to support older |
|
|
22 | operating systems with newer header files/libraries. |
|
|
23 | - prefer gettimeofday over clock_gettime with USE_CLOCK_SYSCALL |
|
|
24 | (default most everywhere), otherwise not. |
|
|
25 | |
|
|
26 | 3.52 Wed Jan 7 21:43:02 CET 2009 |
|
|
27 | - fix compilation of select backend in fd_set mode when NFDBITS is |
|
|
28 | missing (to get it to compile on QNX, reported by Rodrigo Campos). |
|
|
29 | - better select-nfds handling when select backend is in fd_set mode. |
|
|
30 | - diagnose fd_set overruns when select backend is in fd_set mode. |
|
|
31 | - due to a thinko, instead of disabling everything but |
|
|
32 | select on the borked OS X platform, everything but select was |
|
|
33 | allowed (reported by Emanuele Giaquinta). |
|
|
34 | - actually verify that local and remote port are matching in |
|
|
35 | libev's socketpair emulation, which makes denial-of-service |
|
|
36 | attacks harder (but not impossible - it's windows). Make sure |
|
|
37 | it even works under vista, which thinks that getpeer/sockname |
|
|
38 | should return fantasy port numbers. |
|
|
39 | - include "libev" in all assertion messages for potentially |
|
|
40 | clearer diagnostics. |
|
|
41 | - event_get_version (libevent compatibility) returned |
|
|
42 | a useless string instead of the expected version string |
|
|
43 | (patch by W.C.A. Wijngaards). |
|
|
44 | |
|
|
45 | 3.51 Wed Dec 24 23:00:11 CET 2008 |
|
|
46 | - fix a bug where an inotify watcher was added twice, causing |
|
|
47 | freezes on hash collisions (reported and analysed by Graham Leggett). |
|
|
48 | - new config symbol, EV_USE_CLOCK_SYSCALL, to make libev use |
|
|
49 | a direct syscall - slower, but no dependency on librt et al. |
|
|
50 | - assume negative return values != -1 signals success of port_getn |
|
|
51 | (http://cvs.epicsol.org/cgi/viewcvs.cgi/epic5/source/newio.c?rev=1.52) |
|
|
52 | (no known failure reports, but it doesn't hurt). |
|
|
53 | - fork detection in ev_embed now stops and restarts the watcher |
|
|
54 | automatically. |
|
|
55 | - EXPERIMENTAL: default the method to operator () in ev++.h, |
|
|
56 | to make it nicer to use functors (requested by Benedek László). |
|
|
57 | - fixed const object callbacks in ev++.h. |
|
|
58 | - replaced loop_ref argument of watcher.set (loop) by a direct |
|
|
59 | ev_loop * in ev++.h, to avoid clashes with functor patch. |
|
|
60 | - do not try to watch the empty string via inotify. |
|
|
61 | - inotify watchers could be leaked under certain circumstances. |
|
|
62 | - OS X 10.5 is actually even more broken than earlier versions, |
|
|
63 | so fall back to select on that piece of garbage. |
|
|
64 | - fixed some weirdness in the ev_embed documentation. |
| 2 | |
65 | |
| 3 | 3.49 Wed Nov 19 11:26:53 CET 2008 |
66 | 3.49 Wed Nov 19 11:26:53 CET 2008 |
| 4 | - ev_stat watchers will now use inotify as a mere hint on |
67 | - ev_stat watchers will now use inotify as a mere hint on |
| 5 | kernels <2.6.25, or if the filesystem is not in the |
68 | kernels <2.6.25, or if the filesystem is not in the |
| 6 | "known to be good" list. |
69 | "known to be good" list. |
