Lines Matching refs:even

119 C<ev_check> watchers) as well as file watchers (C<ev_stat>) and even
171 These functions can be called anytime, even before initialising the
187 passed (approximately - it might return a bit earlier even if not
268 or even to sleep a while and retry until some memory is available.
418 C<pthread_atfork> which is even faster).
516 totally I<different> file descriptors (even already closed ones, so
517 one cannot even remove them from the set) than registered in the set
616 even sun itself gets it wrong in their code examples: The event polling
617 function sometimes returns events to the caller even though an error
619 even documented that way) - deadly for edge-triggered interfaces where you
630 Try all backends (even potentially broken ones that wouldn't be tried
698 a fork, I<even if you do not plan to use the loop in the parent>. This is
894    ... as they still have work to do (even an idle watcher will do..)
1386 C<ev_clear_pending> will clear the pending event, even if the watcher was
1498 handled first even under adverse conditions (which is usually, but not
1597 because there is no data. It is very easy to get into this situation even
1627 descriptor even if the file descriptor number itself did not change.
1664 to files, even though you should not use it. The reason for this is
1668 F</dev/urandom>), and even though the file might better be served with
1859 It is even possible to change the time-out on the fly, regardless of
1869 It is, however, even simpler than the "obvious" way to do it.
1957 do even better:
2011 501" and invoke the callback 0.1s after it was started, even though a
2096 operating systems, OS versions or even different hardware.
2344 C<ev_periodic_set>, but indeed works even in interval and manual
2415 the signal. You can even use C<ev_async> from a signal handler to
2531 initialised. This is necessary to guarantee proper behaviour even if the
2535 children, even ones not watched.
2549 Currently, the child watcher never gets stopped, even when the
2646 as even with OS-supported change notifications, this can be
2704 time due to network issues, and even under good conditions, a stat call
2713 and even on systems where the resolution is higher, most file systems
2849 (or even signals, imagine) of the same or higher priority it will not be
3151 and even priorities and idle watchers might have too much overhead. In
3319 =head2 C<ev_cleanup> - even the best things end
3376 even without knowing which loop owns the signal.
3500 watcher but the event has not yet been processed (or even noted) by the
3917 can even use F<ev.h> as header file name directly.
3942 will fail and all watchers will have the same priority, even though there
4234 makes rev work even on mingw.
4351 source directory without having to change even a single line in them, so
4456 and in some even more future version the compatibility code will be
4548 it is assumed that all these functions actually work on fds, even
5124 you touch is broken, whether it is locales, poll, kqueue or even the
5163 thread-unsafe that you can't even use components/libraries compiled
5187 this by trying to avoid the poll backend altogether (i.e. it's not even