Lines Matching refs:want

88 it very long. If you just want to know the basics of libev, I suggest
180 you actually want to know. Also interesting is the combination of
201 C<ev_version_minor>. If you want, you can compare against the global
355 Note that this function is I<not> thread-safe, so if you want to use it
451 when you want to receive them.
453 This behaviour is useful when you want to do your own signal handling, or
454 want to handle signals only in specific threads and want to avoid libev
473 connections as possible during one iteration. You might also want to have
641 C<flags> value, in case you want to mask out any backends from a flags
694 In addition, if you want to reuse a loop (via this function or
697 Again, you I<have> to call it on I<any> loop that you want to re-use after
703 process if and only if you want to use the event loop in the child. If
808 after you have initialised all your watchers and you want to start
1010 when you want to do some lengthy calculation and want to pass further
1023 this callback instead. This is useful, for example, when you want to
1026 If you want to reset the callback, use C<ev_invoke_pending> as new
1031 Sometimes you want to share the same loop between multiple threads. This
1051 waited. Use an C<ev_async> watcher to wake up C<ev_run> when you want it
1095 your interest in some event. To make a concrete example, imagine you want
1196 they want, and all of them will be taken into account (for example, a
1309 pending. If you want to free or reuse the memory used by the watcher it is
1499 always, what you want).
1586 the watcher if you don't want to act on the event and neither want to
1590 fd as you want (as long as you don't confuse yourself). Setting all file
1665 convenience: sometimes you want to watch STDIN or STDOUT, which is
1674 when you rarely read from a file instead of from a socket, and want to
1681 it in the child if you want to continue to use it in the child.
1803 you want to raise some error after a while.
1866 you want to modify its timeout value, as libev does not have to completely
2060 C<ev_time ()> and C<ev_now ()>, at least if you want better precision than
2076 If you want to compare wall clock/system timestamps to your timers, then
2413 If you want signals to be delivered truly asynchronously, just use
2470 When you want to use sigwait (or mix libev signal handling with your own
2930 you cache some data and want to flush it before blocking (for example,
2931 in X programs you might want to do an C<XFlush ()> in an C<ev_prepare>
2969 example, if you want to handle a large number of connections fairly, you
3098 want to embed is not flexible enough to support it. Instead, you can
3137 There are primarily two reasons you would want that: work around bugs and
3142 still want to make use of it because you have many sockets and it scales
3147 best: C<kqueue> for scalable sockets and C<poll> if you want it to work :)
3174 So when you want to use this feature you will always have to be prepared
3199 if you do not want that, you need to temporarily stop the embed watcher).
3286 When both processes want to continue using libev, then this is usually the
3298 When this is not possible, or you want to use the default loop for
3327 loop when you want them to be invoked.
3386 That means that if you want to queue data, you have to provide your own
3526 watchers. This is useful if you want to wait for a single event on an fd
3581 don't want to allocate memory separately and store a pointer to it in that
3667 might want to do something to the request after starting it, such as
3690 This brings the problem of exiting - a callback might want to finish the
3843 Whenever you want to start/stop a watcher or do other modifications to an
3865 kind of threads or coroutines, you might want to customise libev so that
4410 in the files that want to use the libevent API. This also includes F<ev.h>.
4420 whatever way you want, you can also C<m4_include([libev.m4])> in your
4671 occasionally useful if you want to provide your own wrapper functions
4719 with some broad features you want) and then selectively re-enable
4720 additional parts you want, for example if you want everything minimal,
4772 Enables all optional watcher types.  If you want to selectively enable
4804 when you embed libev, only want to use libev functions in a single file,
4805 and do not want its identifiers to be visible.
4838 might want to increase this value (I<must> be a power of two).
4845 C<ev_stat> watchers you might want to increase this value (I<must> be a
4973 that you can use as many loops as you want in parallel, as long as there
4990 If you want to know which design (one loop, locking, or multiple loops
5167 If you want to use libev in threaded environments you have to make sure