| 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 | |
2 | |
| 3 | TODO: ev_walk |
3 | - backport inotify code to C89. |
| 4 | TODO: signal handling per loop |
4 | - implement EV_WIN32_HANDLE_TO_FD and EV_WIN32_CLOSE_FD configuration |
| 5 | TODO: signalfd |
5 | symbols to make ti easier for apps to do their own fd management. |
|
|
6 | - support EV_IDLE_ENABLE being disabled in ev++.h |
|
|
7 | (patch by Didier Spezia). |
| 6 | |
8 | |
| 7 | TODO: document signalfd procmask |
9 | 3.8 Sun Aug 9 14:30:45 CEST 2009 |
| 8 | - incompatible change: do not necessarily reset signal handler |
10 | - incompatible change: do not necessarily reset signal handler |
| 9 | to SIG_DFL when a sighandler is stopped. |
11 | to SIG_DFL when a sighandler is stopped. |
|
|
12 | - ev_default_destroy did not properly free or zero some members, |
|
|
13 | potentially causing crashes and memory corruption on repated |
|
|
14 | ev_default_destroy/ev_default_loop calls. |
| 10 | - take advantage of signalfd on GNU/Linux systems. |
15 | - take advantage of signalfd on GNU/Linux systems. |
| 11 | - document that the signal mask might be in an unspecified |
16 | - document that the signal mask might be in an unspecified |
| 12 | state when using libev's signal handling. |
17 | state when using libev's signal handling. |
|
|
18 | - take advantage of some GNU/Linux calls to set cloexec/nonblock |
|
|
19 | on fd creation, to avoid race conditions. |
| 13 | |
20 | |
| 14 | 3.7 Fri Jul 17 16:36:32 CEST 2009 |
21 | 3.7 Fri Jul 17 16:36:32 CEST 2009 |
| 15 | - ev_unloop and ev_loop wrongly used a global variable to exit loops, |
22 | - ev_unloop and ev_loop wrongly used a global variable to exit loops, |
| 16 | instead of using a per-loop variable (bug caught by accident...). |
23 | instead of using a per-loop variable (bug caught by accident...). |
| 17 | - the ev_set_io_collect_interval interpretation has changed. |
24 | - the ev_set_io_collect_interval interpretation has changed. |
