diff options
author | root <root> | 2007-12-08 14:12:07 +0000 |
---|---|---|
committer | root <root> | 2007-12-08 14:12:07 +0000 |
commit | 480621758fe1687120978562a553920ed46e1b7e (patch) | |
tree | 12e3f18a656864a877d1b3738f9fb74be1bd862b /ev.pod | |
parent | 74ab025f4b269ca1365059e6e07834e452adfabc (diff) |
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r-- | ev.pod | 12 |
1 files changed, 12 insertions, 0 deletions
@@ -779,6 +779,18 @@ Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is fine, as long as you do not mind that the priority value you query might or might not have been adjusted to be within valid range. +=item ev_invoke (loop, ev_TYPE *watcher, int revents) + +Invoke the C<watcher> with the given C<loop> and C<revents>. Neither +C<loop> nor C<revents> need to be valid as long as the watcher callback +can deal with that fact. + +=item int ev_clear_pending (loop, ev_TYPE *watcher) + +If the watcher is pending, this function returns clears its pending status +and returns its C<revents> bitset (as if its callback was invoked). If the +watcher isn't pending it does nothing and returns C<0>. + =back |