Lines Matching refs:pending

857    - Before the first iteration, call any pending watchers.
877    - Queue all idle watchers with priority higher than that of pending events.
1006 This call will simply invoke all pending watchers while resetting their
1007 pending state. Normally, C<ev_run> does this automatically when required,
1016 Returns the number of pending watchers - zero indicates that no watchers
1017 are pending.
1021 This overrides the invoke pending functionality of the loop: Instead of
1022 invoking all pending watchers when there are any, C<ev_run> will call
1257 (or never started) and there are no pending events outstanding.
1273 macro on a watcher that is active (it can be pending, however, which is a
1303 Stops the given watcher if active, and clears the pending status (whether
1306 It is possible that stopped watchers are pending - for example,
1307 non-repeating timers are being stopped when they become pending - but
1309 pending. If you want to free or reuse the memory used by the watcher it is
1320 Returns a true value iff the watcher is pending, (i.e. it has outstanding
1322 is pending (but not active) you must not call an init function on it (but
1346 If you need to suppress invocation when higher priority events are pending
1350 pending.
1371 If the watcher is pending, this function clears its pending status and
1373 watcher isn't pending it does nothing and returns C<0>.
1383 not free the watcher as long as it has pending events.
1386 C<ev_clear_pending> will clear the pending event, even if the watcher was
1400 active, pending and so on. In this section these states and the rules to
1425 =item pending
1428 in has occurred (such as a timer expiring), it will become pending. It will
1429 stay in this pending state until either it is stopped or its callback is
1430 about to be invoked, so it is not normally pending inside the watcher
1433 The watcher might or might not be active while it is pending (for example,
1434 an expired non-repeating timer can be pending but no longer active). If it
1441 via C<ev_feed_event>), in which case it becomes pending without being
1447 be pending), or explicitly by calling its C<ev_TYPE_stop> function. The
1448 latter will clear any pending state the watcher might be in, regardless
1452 While stopped (and not pending) the watcher is essentially in the
1522 other events are pending:
1702 connection from the pending queue in all error cases.
2141 =item If the timer is pending, the pending status is always cleared.
2845 priority are pending (prepare, check and other idle watchers do not count
2851 are pending), the idle watchers are being called once per event loop
2938 you check for any events that occurred (by checking the pending status
3156 time there might be events pending in the embedded loop. The callback
3508 Not that this does I<not> check whether the watcher itself is pending,
3509 only whether it has been requested to make this watcher pending: there
3676 pushing it into the pending queue:
3809 Instead of invoking all pending watchers, the C<l_invoke> callback will
3811 writes? C<Async::Interrupt>?) and then waits until all pending watchers
3813 and b) skipping inter-thread-communication when there are no pending
3828 Now, whenever the main thread gets told to invoke pending watchers, it
4132 do this when the watcher is inactive (and not pending either).
5405 =item Activating one watcher (putting it into the pending state): O(1)
5538 =item pending
5540 A watcher is pending as soon as the corresponding event has been