Lines Matching refs:again

819 (which usually means " you should call C<ev_run> again").
941 Example: For some weird reason, unregister the above signal handler again.
994 times the process sleeps and wakes up again. Another useful technique to
1045 C<acquire> will just call the mutex_lock function again.
1415 C<ev_TYPE_init> again.
1455 it again).
1486 libraries will just poll for the same events again and again as long as
1546      // have to start the I/O watcher again, as
1707 the next iteration again (the connection still exists after all), and
1823 and start it again:
1831 data structure and then add it again. Libev tries to be fast, but it's
1921 again at the earliest time it could time out. Rinse. Repeat.
1944 will again do the right thing (for example, time out immediately :).
1966 the timeout, append it to the end of the list again, and make sure to
2103 use, then libev will again assume a timejump and adjust accordingly.
2121 configured to trigger again C<repeat> seconds later, again, and again,
2132 This will act as if the timer timed out, and restarts it again if it is
2203    // reset the timeout to start ticking again at 10 seconds
2328 you do this is, again, up to you (but it is not trivial, which is the main
2335 Simply stops and restarts the periodic watcher again. This is only useful
2438 stopping it again), that is, libev might or might not block the signal,
2853 and becomes busy again with higher priority stuff.
3118      // stop timer again
3122      // stop io watchers again - their callbacks should have set
3505 it will reset the flag again. C<ev_async_pending> can be used to very
4160 =item w->again () (C<ev::timer>, C<ev::periodic> only)
4570 file descriptors again. Note that the replacement function has to close
5376 =item Changing timer/periodic watchers (by autorepeat or calling again): O(log skipped_other_timers)