Lines Matching refs:value

143 any calculations on it, you should treat it as some floating point value.
224 value) compiled into this binary of libev (independent of their
247 value is platform-specific but can include backends not available on the
394 The default flags value. Use this if you have no clue (it's the right
399 If this flag bit is or'ed into the flag value (or the program runs setuid
462 =item C<EVBACKEND_SELECT>  (value 1, portable select backend)
481 =item C<EVBACKEND_POLL>    (value 2, poll backend, available everywhere except on windows)
493 =item C<EVBACKEND_EPOLL>   (value 4, Linux)
507 returning before the timeout value, resulting in additional iterations
556 =item C<EVBACKEND_KQUEUE>  (value 8, most BSD clones)
593 =item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)
600 =item C<EVBACKEND_PORT>    (value 32, Solaris 10)
641 C<flags> value, in case you want to mask out any backends from a flags
642 value (e.g. when modifying the C<LIBEV_FLAGS> environment variable).
646 If one or more of the backend flags are or'ed into the flags value,
735 This value can sometimes be useful as a generation counter of sorts (it
817 The return value is false if there are no more active watchers (which
830 exception and so on. This does not decrement the C<ev_depth> value, nor
833 A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
839 A flags value of C<EVRUN_ONCE> will look for new events (waiting if
955 Setting these to a higher value (the C<interval> I<must> be >= C<0>)
969 C<ev_timer>) will not be affected. Setting this to a non-null value will
979 value will not introduce any overhead in libev.
982 interval to a value near C<0.1> or so, which is often enough for
984 usually doesn't make much sense to set it to a lower value than C<0.01>,
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
1353 fine, as long as you do not mind that the priority value you query might
1839 To implement this, configure an C<ev_timer> with a C<repeat> value
1866 you want to modify its timeout value, as libev does not have to completely
1913 If this value is negative, then we are already past the timeout, i.e. we
1917 and simply start the timer with this timeout value.
1942 When your timeout value changes, then the timeout can be changed by simply
1943 providing a new value, stopping the timer and calling the callback, which
1956 employing some kind of timeout with the same timeout value, then one can
1959 When starting the timeout, calculate the timeout value and put the timeout
2134 timeout to the C<repeat> value and calling C<ev_timer_start>.
2146 =item If the timer is repeating, make the C<repeat> value the new timeout
2158 the timeout value currently configured.
2168 The current C<repeat> value. Will be used each time the watcher times out
2282 interval value should be higher than C<1/8192> (which is around 100
2317 It must return the next time to trigger, based on the passed time value
2318 (that is, the lowest time value larger than to the second argument). It
2323 equal to the passed C<now> value >>.
2327 next midnight after C<now> and return the timestamp value for this. How
2349 When repeating, this contains the offset value, otherwise this is the
2350 absolute point in time (the C<offset> value passed to C<ev_periodic_set>,
2351 although libev might modify this value for better numerical stability).
2358 The current interval value. Can be modified any time, but changes only
2640 recommended!) then a I<suitable, unspecified default> value will be used
2747 a suitable value. The memory pointed to by C<path> must point to the same
3226    // (remember that a flags value of 0 means autodetection)
3499 Returns a non-zero value when C<ev_async_send> has been called on the
3541 value passed to C<ev_once>. Note that it is possible to receive I<both>
4309 Similar to the other two macros, this gives you the value of the default
4497 C<EV_USE_MONOTONIC>, though. Defaults to the opposite value of
4564 to do so. This can be done by defining this macro to an appropriate value.
4730 The actual value is a bitset, it can be a combination of the following
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
5307 Accessing a pointer value must be atomic, it must both be readable and
5338 =item C<double> must hold a time value in seconds with enough accuracy