| … | |
… | |
| 777 | |
777 | |
| 778 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
778 | Setting a priority outside the range of C<EV_MINPRI> to C<EV_MAXPRI> is |
| 779 | fine, as long as you do not mind that the priority value you query might |
779 | fine, as long as you do not mind that the priority value you query might |
| 780 | or might not have been adjusted to be within valid range. |
780 | or might not have been adjusted to be within valid range. |
| 781 | |
781 | |
|
|
782 | =item ev_invoke (loop, ev_TYPE *watcher, int revents) |
|
|
783 | |
|
|
784 | Invoke the C<watcher> with the given C<loop> and C<revents>. Neither |
|
|
785 | C<loop> nor C<revents> need to be valid as long as the watcher callback |
|
|
786 | can deal with that fact. |
|
|
787 | |
|
|
788 | =item int ev_clear_pending (loop, ev_TYPE *watcher) |
|
|
789 | |
|
|
790 | If the watcher is pending, this function returns clears its pending status |
|
|
791 | and returns its C<revents> bitset (as if its callback was invoked). If the |
|
|
792 | watcher isn't pending it does nothing and returns C<0>. |
|
|
793 | |
| 782 | =back |
794 | =back |
| 783 | |
795 | |
| 784 | |
796 | |
| 785 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
797 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
| 786 | |
798 | |
