Lines Matching refs:flags

339 =item struct ev_loop *ev_default_loop (unsigned int flags)
343 the C<flags> parameter are described in more detail in the entry for
347 returns it (and ignores the flags. If that is troubling you, check
349 flags, which should almost always be C<0>, unless the caller is also the
376 =item struct ev_loop *ev_loop_new (unsigned int flags)
385 The flags argument can be used to specify special behaviour or specific
388 The following flags are supported:
394 The default flags value. Use this if you have no clue (it's the right
402 override the flags completely if it is found in the environment. This is
564 "auto-detected" unless you explicitly specify it in the flags (i.e. using
641 C<flags> value, in case you want to mask out any backends from a flags
646 If one or more of the backend flags are or'ed into the flags value,
756 Returns one of the C<EVBACKEND_*> flags indicating the event backend in
805 =item bool ev_run (loop, int flags)
813 If the flags argument is specified as C<0>, it will keep handling events
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
2661 compile libev with the same flags to get binary compatibility. This is
2662 obviously the case with any flags that change the ABI, but the problem is
3055          // set the relevant poll flags
3226    // (remember that a flags value of 0 means autodetection)
4742 When optimising for size, use of compiler flags such as C<-Os> with