Lines Matching refs:s

33      // this causes all nested ev_run's to stop iterating
208 Usually, it's a good idea to terminate if the major versions mismatch,
394 The default flags value. Use this if you have no clue (it's the right
444 there are a lot of shoddy libraries and programs (glib's threadpool for
457 It's also required by POSIX in a threaded program, as libev calls
460 This flag's behaviour will become the default in future versions of libev.
483 And this is your standard poll(2) backend. It's more complicated
561 it's completely useless). Unlike epoll, however, whose brokenness
563 without API changes to existing programs. For this reason it's not being
577 might have to leak fd's on fork, but it's more sane than epoll) and it
603 it's really slow, but it still scales very well (O(active_fds)).
618 occurred, but with no indication whether it has done so or not (yes, it's
709 The function itself is quite fast and it's usually not a problem to call
751 as a hint to avoid such ungentleman-like behaviour unless it's really
774 very long time without entering the event loop, updating libev's idea of
961 one (or very few) event(s) per loop iteration. While this makes the
998 Example: we only need 0.1s timeout granularity, and we wish not to poll
1048 C<release> and C<acquire> (that's their only purpose after all), no
1652 there, and in the case of open files, that's always the case, so you
1718 event-based way to handle this situation, so it's the best one can do.
1831 data structure and then add it again. Libev tries to be fast, but it's
1985 off after the first million or so of active timers, i.e. it's usually
2010 If an event library looks at the timeout 0.1s later, it will see "501 >=
2011 501" and invoke the callback 0.1s after it was started, even though a
2018 the callback at system time 502, or 1.1s after the timer was started.
2068 This is because C<ev_timer>s work in real time, not wall clock time, so
2077 you need to use C<ev_periodic>s, as these are based on the wall clock
2101 then you can expect C<ev_timer>s to expire as the full suspension time
2157 then this time is relative to the current event loop time, otherwise it's
2246 Lots of arguments, let's sort it out... There are basically three modes of
2540 processing, but if your application collides with libev's default child
2544 event-based approach to child reaping and thus use libev's support for
2622 if it did. Starting the watcher C<stat>'s the file, so only changes that
2643 currently around C<0.1>, but that's usually overkill.
2699 busy or the intervals between stat's are large, a stat call will be fast,
2826      /* now it's one second after the most recent passwd change */
2946 are ready to run (it's actually more complicated: it only runs coroutines
3658 It's not uncommon to have code paths in C<start_new_request> that
3903 To embed libev, see L</EMBEDDING>, but in short, it's easiest to create two
4117 callback. The optional C<data> argument will be stored in the watcher's
4378 compiler (at least, that's a stated goal, and breakage will be treated
4659 F<ev.c>'s idea of where to find the F<config.h> file, similarly to
4664 Similarly to C<EV_H>, this macro can be used to override F<event.c>'s idea
4924 A sed command like this will create wrapper C<#define>'s that you need to
4927    <Symbols.ev sed -e "s/.*/#define & myprefix_&/" >wrap.h
5149 All that's left is C<select>, and of course Apple found a way to fuck this
5168 it's compiled with C<_REENTRANT> defined.
5187 this by trying to avoid the poll backend altogether (i.e. it's not even
5268 Early versions of winsocket's select only supported waiting for a maximum