diff options
author | root <root> | 2008-09-30 19:51:44 +0000 |
---|---|---|
committer | root <root> | 2008-09-30 19:51:44 +0000 |
commit | c53135daec2ac56c937fc5d516031ecbaebdb956 (patch) | |
tree | c25da5aee2f80d46cf9644aea6720e20ff19602f | |
parent | 3329653c7d595f6cbc31f831ce7f7e9e4c238a04 (diff) |
*** empty log message ***
-rw-r--r-- | Changes | 1 | ||||
-rw-r--r-- | ev.pod | 8 |
2 files changed, 5 insertions, 4 deletions
@@ -1,6 +1,7 @@ Revision history for libev, a high-performance and full-featured event loop. WISH? monotonic clocks times/GetTickCount for coarse corrections? +TODO: make ev_once timeout=0 useful, and make I/O always win. 3.44 Mon Sep 29 05:18:39 CEST 2008 - embed watchers now automatically invoke ev_loop_fork on the embedded loop when the parent loop forks. @@ -2504,14 +2504,14 @@ There are some other functions of possible interest. Described. Here. Now. =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) This function combines a simple timer and an I/O watcher, calls your -callback on whichever event happens first and automatically stop both +callback on whichever event happens first and automatically stops both watchers. This is useful if you want to wait for a single event on an fd or timeout without having to allocate/configure/start/stop/free one or more watchers yourself. -If C<fd> is less than 0, then no I/O watcher will be started and events -is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and -C<events> set will be created and started. +If C<fd> is less than 0, then no I/O watcher will be started and the +C<events> argument is being ignored. Otherwise, an C<ev_io> watcher for +the given C<fd> and C<events> set will be created and started. If C<timeout> is less than 0, then no timeout watcher will be started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |