Lines Matching refs:e

146 time differences (e.g. delays) throughout libev.
223 Return the set of all backends (i.e. their corresponding C<EV_BACKEND_*>
487 i.e. O(total_fds). See the entry for C<EVBACKEND_SELECT>, above, for
540 i.e. keep at least one watcher active per fd at all times. Stopping and
564 "auto-detected" unless you explicitly specify it in the flags (i.e. using
586 (e.g. C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> (but C<poll> is of course
642 value (e.g. when modifying the C<LIBEV_FLAGS> environment variable).
666 sense, so e.g. C<ev_is_active> might still return true. It is your
847 with something not expressible using other libev watchers (i.e. "roll your
879    - Call all queued watchers in reverse order (i.e. check watchers first).
930 (e.g. non-repeating timers) in which case you have to C<ev_ref>
1049 modifications done will affect the event loop, i.e. adding watchers will
1091 watcher type, e.g. C<ev_TYPE_start> can mean C<ev_timer_start> for timer
1220 by libev users to signal watchers (e.g. via C<ev_feed_event>).
1277 (e.g. C<ev_prepare>) you still need to call its C<set> macro.
1314 Returns a true value iff the watcher is active (i.e. it has been started
1320 Returns a true value iff the watcher is pending, (i.e. it has outstanding
1324 make sure the watcher is available to libev (e.g. you cannot C<free ()>
1435 is stopped, it can be freely accessed (e.g. by calling C<ev_TYPE_set>),
1440 It is also possible to feed an event on a watcher that is not active (e.g.
1614 Some backends (e.g. kqueue, epoll) need to be told about closing a file
1635 Some backends (e.g. epoll), cannot register events for file descriptors,
1672 So avoid file descriptors pointing to files when you know it (e.g. use
1673 libeio), but use them when it is convenient, e.g. for STDIN/STDOUT, or
1728 descriptor for overload situations (e.g. by opening F</dev/null>), and
1809 gets reset to 60 seconds each time there is activity (e.g. each time some
1913 If this value is negative, then we are already past the timeout, i.e. we
1985 off after the first million or so of active timers, i.e. it's usually
2072 If your timeouts are based on a physical timescale (e.g. "time out this
2216 time, and time jumps are not uncommon (e.g. when you adjust your
2221 seconds" (by specifying e.g. C<ev_now () + 10.>, that is, an absolute time
2305 it afterwards (e.g. by starting an C<ev_prepare> watcher, which is the
2309 *w, ev_tstamp now)>, e.g.:
2337 a different time than the last time it was called (e.g. in a crond like
2410 will try its best to deliver signals synchronously, i.e. as part of the
2419 only within the same loop, i.e. you can watch for C<SIGINT> in your
2516 as the event loop isn't entered (or is continued from a watcher), i.e.,
2666 file interfaces available by default (as e.g. FreeBSD does) and not
2683 many bugs), the path exists (i.e. stat succeeds), and the path resides on
2720 stat data does change in other ways (e.g. file size).
2724 a roughly one-second-delay C<ev_timer> (e.g. C<ev_timer_set (w, 0., 1.02);
2922 for recursion in those watchers, i.e. the sequence will always be
3032      ev_timer_init (&tw, 0, timeout * 1e-3, 0.);
3144 it into your default loop (which might use e.g. poll). Overall operation
3166 is active, i.e., the embedded loop will automatically be forked when the
3289 process typically wants to start fresh, i.e. without any active watchers.
3372 (i.e. the number of callback invocations may be less than the number of
3691 main C<ev_run> call, but not the nested one (e.g. user clicked "Quit", but
3693 and not the main one (e.g. user clocked "Ok" in a modal dialog), or some
3863 While the overhead of a callback that e.g. schedules a thread is small, it
4071 callback (i.e. it is visible to it at the place of the C<set> call and
4382 in your include path (e.g. in libev/ when using -Ilibev):
4747 (e.g. gcc with C<-Os>).
4757 (e.g. gcc with C<-Os>).
4773 only some watcher types other than I/O and timers (e.g. prepare,
4913 If you need to re-export the API (e.g. via a DLL) and you need a list of
4927    <Symbols.ev sed -e "s/.*/#define & myprefix_&/" >wrap.h
4982 only one thread ever is inside a call at any point in time, e.g. by using
5032 coroutines (e.g. you can call C<ev_run> on the same loop from two
5066 them (e.g. by ignoring them). Remember that warnings are just that:
5086 as if it were a bug in libev (e.g. in realloc or in the poll backend,
5119 i.e. all programs not using special compile switches.
5187 this by trying to avoid the poll backend altogether (i.e. it's not even
5195 Win32 doesn't support any of the standards (e.g. POSIX) that libev
5200 e.g. cygwin. Actually, it only applies to the microsofts own compilers,
5275 to some high number (e.g. C<2048>) before compiling the winsocket select
5550 be wrong and jump forwards and backwards, e.g. when you adjust your