Lines Matching refs:new

378 This will create and initialise a new event loop object. If the loop
704 you just fork+exec or create a new loop in the child, you don't have to
732 to the number of times libev did poll for new events. It starts at C<0>
809 handling events. It will ask the operating system for any new events, call
833 A flags value of C<EVRUN_NOWAIT> will look for new events, will handle
836 iteration of the loop. This is sometimes useful to poll and handle new
839 A flags value of C<EVRUN_ONCE> will look for new events (waiting if
841 will block your process until at least one new event arrives (which could
962 program responsive, it also wastes a lot of CPU time to poll for new
1026 If you want to reset the callback, use C<ev_invoke_pending> as new
1041 suspended waiting for new events, and C<acquire> is called just
1188 gather new events, and all C<ev_check> watchers are queued (not invoked)
1191 watchers invoked before the event loop sleeps or polls for new events, and
1479 before polling for new events.
1624 will assume that this is potentially a new file descriptor, otherwise
1730 close that fd, and create a new dummy fd. This will gracefully refuse
1943 providing a new value, stopping the timer and calling the callback, which
2029 time only before and after C<ev_run> collects new events, which causes a
2146 =item If the timer is repeating, make the C<repeat> value the new timeout
2589 Example: C<fork()> a new process and install a child handler to wait for
2756 Updates the stat buffer immediately with new values. If you change the
2760 new values.
2856 active, the process will not block when waiting for new events.
3292 simply create a new event loop, which of course will be "empty", and
3293 use that for new watchers. This has the advantage of not touching more
3767 solely to wake up the event loop so it takes notice of any new watchers
3858 about the newly added timer. By waking up the loop it will pick up any new
5435 new API early than late.