… | |
… | |
39 | F<README.embed> in the libev distribution. If libev was configured without |
39 | F<README.embed> in the libev distribution. If libev was configured without |
40 | support for multiple event loops, then all functions taking an initial |
40 | support for multiple event loops, then all functions taking an initial |
41 | argument of name C<loop> (which is always of type C<struct ev_loop *>) |
41 | argument of name C<loop> (which is always of type C<struct ev_loop *>) |
42 | will not have this argument. |
42 | will not have this argument. |
43 | |
43 | |
44 | =head1 TIME AND OTHER GLOBAL FUNCTIONS |
44 | =head1 TIME REPRESENTATION |
45 | |
45 | |
46 | Libev represents time as a single floating point number, representing the |
46 | Libev represents time as a single floating point number, representing the |
47 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
47 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
48 | the beginning of 1970, details are complicated, don't ask). This type is |
48 | the beginning of 1970, details are complicated, don't ask). This type is |
49 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
49 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
50 | to the double type in C. |
50 | to the double type in C. |
|
|
51 | |
|
|
52 | =head1 GLOBAL FUNCTIONS |
|
|
53 | |
|
|
54 | These functions can be called anytime, even before initialising the |
|
|
55 | library in any way. |
51 | |
56 | |
52 | =over 4 |
57 | =over 4 |
53 | |
58 | |
54 | =item ev_tstamp ev_time () |
59 | =item ev_tstamp ev_time () |
55 | |
60 | |
… | |
… | |
99 | An event loop is described by a C<struct ev_loop *>. The library knows two |
104 | An event loop is described by a C<struct ev_loop *>. The library knows two |
100 | types of such loops, the I<default> loop, which supports signals and child |
105 | types of such loops, the I<default> loop, which supports signals and child |
101 | events, and dynamically created loops which do not. |
106 | events, and dynamically created loops which do not. |
102 | |
107 | |
103 | If you use threads, a common model is to run the default event loop |
108 | If you use threads, a common model is to run the default event loop |
104 | in your main thread (or in a separate thrad) and for each thread you |
109 | in your main thread (or in a separate thread) and for each thread you |
105 | create, you also create another event loop. Libev itself does no locking |
110 | create, you also create another event loop. Libev itself does no locking |
106 | whatsoever, so if you mix calls to the same event loop in different |
111 | whatsoever, so if you mix calls to the same event loop in different |
107 | threads, make sure you lock (this is usually a bad idea, though, even if |
112 | threads, make sure you lock (this is usually a bad idea, though, even if |
108 | done correctly, because it's hideous and inefficient). |
113 | done correctly, because it's hideous and inefficient). |
109 | |
114 | |
… | |
… | |
299 | |
304 | |
300 | As long as your watcher is active (has been started but not stopped) you |
305 | As long as your watcher is active (has been started but not stopped) you |
301 | must not touch the values stored in it. Most specifically you must never |
306 | must not touch the values stored in it. Most specifically you must never |
302 | reinitialise it or call its set method. |
307 | reinitialise it or call its set method. |
303 | |
308 | |
304 | You cna check whether an event is active by calling the C<ev_is_active |
309 | You can check whether an event is active by calling the C<ev_is_active |
305 | (watcher *)> macro. To see whether an event is outstanding (but the |
310 | (watcher *)> macro. To see whether an event is outstanding (but the |
306 | callback for it has not been called yet) you cna use the C<ev_is_pending |
311 | callback for it has not been called yet) you can use the C<ev_is_pending |
307 | (watcher *)> macro. |
312 | (watcher *)> macro. |
308 | |
313 | |
309 | Each and every callback receives the event loop pointer as first, the |
314 | Each and every callback receives the event loop pointer as first, the |
310 | registered watcher structure as second, and a bitset of received events as |
315 | registered watcher structure as second, and a bitset of received events as |
311 | third argument. |
316 | third argument. |
312 | |
317 | |
313 | The rceeived events usually include a single bit per event type received |
318 | The received events usually include a single bit per event type received |
314 | (you can receive multiple events at the same time). The possible bit masks |
319 | (you can receive multiple events at the same time). The possible bit masks |
315 | are: |
320 | are: |
316 | |
321 | |
317 | =over 4 |
322 | =over 4 |
318 | |
323 | |
… | |
… | |
372 | =back |
377 | =back |
373 | |
378 | |
374 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
379 | =head2 ASSOCIATING CUSTOM DATA WITH A WATCHER |
375 | |
380 | |
376 | Each watcher has, by default, a member C<void *data> that you can change |
381 | Each watcher has, by default, a member C<void *data> that you can change |
377 | and read at any time, libev will completely ignore it. This cna be used |
382 | and read at any time, libev will completely ignore it. This can be used |
378 | to associate arbitrary data with your watcher. If you need more data and |
383 | to associate arbitrary data with your watcher. If you need more data and |
379 | don't want to allocate memory and store a pointer to it in that data |
384 | don't want to allocate memory and store a pointer to it in that data |
380 | member, you can also "subclass" the watcher type and provide your own |
385 | member, you can also "subclass" the watcher type and provide your own |
381 | data: |
386 | data: |
382 | |
387 | |
… | |
… | |
409 | =head2 C<ev_io> - is this file descriptor readable or writable |
414 | =head2 C<ev_io> - is this file descriptor readable or writable |
410 | |
415 | |
411 | I/O watchers check whether a file descriptor is readable or writable |
416 | I/O watchers check whether a file descriptor is readable or writable |
412 | in each iteration of the event loop (This behaviour is called |
417 | in each iteration of the event loop (This behaviour is called |
413 | level-triggering because you keep receiving events as long as the |
418 | level-triggering because you keep receiving events as long as the |
414 | condition persists. Remember you cna stop the watcher if you don't want to |
419 | condition persists. Remember you can stop the watcher if you don't want to |
415 | act on the event and neither want to receive future events). |
420 | act on the event and neither want to receive future events). |
416 | |
421 | |
417 | In general you can register as many read and/or write event watchers oer |
422 | In general you can register as many read and/or write event watchers oer |
418 | fd as you want (as long as you don't confuse yourself). Setting all file |
423 | fd as you want (as long as you don't confuse yourself). Setting all file |
419 | descriptors to non-blocking mode is also usually a good idea (but not |
424 | descriptors to non-blocking mode is also usually a good idea (but not |
420 | required if you know what you are doing). |
425 | required if you know what you are doing). |
421 | |
426 | |
422 | You have to be careful with dup'ed file descriptors, though. Some backends |
427 | You have to be careful with dup'ed file descriptors, though. Some backends |
423 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
428 | (the linux epoll backend is a notable example) cannot handle dup'ed file |
424 | descriptors correctly if you register interest in two or more fds pointing |
429 | descriptors correctly if you register interest in two or more fds pointing |
425 | to the same file/socket etc. description. |
430 | to the same file/socket etc. description (that is, they share the same |
|
|
431 | underlying "file open"). |
426 | |
432 | |
427 | If you must do this, then force the use of a known-to-be-good backend |
433 | If you must do this, then force the use of a known-to-be-good backend |
428 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
434 | (at the time of this writing, this includes only EVMETHOD_SELECT and |
429 | EVMETHOD_POLL). |
435 | EVMETHOD_POLL). |
430 | |
436 | |
… | |
… | |
444 | |
450 | |
445 | Timer watchers are simple relative timers that generate an event after a |
451 | Timer watchers are simple relative timers that generate an event after a |
446 | given time, and optionally repeating in regular intervals after that. |
452 | given time, and optionally repeating in regular intervals after that. |
447 | |
453 | |
448 | The timers are based on real time, that is, if you register an event that |
454 | The timers are based on real time, that is, if you register an event that |
449 | times out after an hour and youreset your system clock to last years |
455 | times out after an hour and you reset your system clock to last years |
450 | time, it will still time out after (roughly) and hour. "Roughly" because |
456 | time, it will still time out after (roughly) and hour. "Roughly" because |
451 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
457 | detecting time jumps is hard, and soem inaccuracies are unavoidable (the |
452 | monotonic clock option helps a lot here). |
458 | monotonic clock option helps a lot here). |
453 | |
459 | |
454 | The relative timeouts are calculated relative to the C<ev_now ()> |
460 | The relative timeouts are calculated relative to the C<ev_now ()> |
455 | time. This is usually the right thing as this timestamp refers to the time |
461 | time. This is usually the right thing as this timestamp refers to the time |
456 | of the event triggering whatever timeout you are modifying/starting. If |
462 | of the event triggering whatever timeout you are modifying/starting. If |
457 | you suspect event processing to be delayed and you *need* to base the timeout |
463 | you suspect event processing to be delayed and you *need* to base the timeout |
458 | ion the current time, use something like this to adjust for this: |
464 | on the current time, use something like this to adjust for this: |
459 | |
465 | |
460 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
466 | ev_timer_set (&timer, after + ev_now () - ev_time (), 0.); |
461 | |
467 | |
462 | =over 4 |
468 | =over 4 |
463 | |
469 | |
… | |
… | |
471 | later, again, and again, until stopped manually. |
477 | later, again, and again, until stopped manually. |
472 | |
478 | |
473 | The timer itself will do a best-effort at avoiding drift, that is, if you |
479 | The timer itself will do a best-effort at avoiding drift, that is, if you |
474 | configure a timer to trigger every 10 seconds, then it will trigger at |
480 | configure a timer to trigger every 10 seconds, then it will trigger at |
475 | exactly 10 second intervals. If, however, your program cannot keep up with |
481 | exactly 10 second intervals. If, however, your program cannot keep up with |
476 | the timer (ecause it takes longer than those 10 seconds to do stuff) the |
482 | the timer (because it takes longer than those 10 seconds to do stuff) the |
477 | timer will not fire more than once per event loop iteration. |
483 | timer will not fire more than once per event loop iteration. |
478 | |
484 | |
479 | =item ev_timer_again (loop) |
485 | =item ev_timer_again (loop) |
480 | |
486 | |
481 | This will act as if the timer timed out and restart it again if it is |
487 | This will act as if the timer timed out and restart it again if it is |
… | |
… | |
495 | state where you do not expect data to travel on the socket, you can stop |
501 | state where you do not expect data to travel on the socket, you can stop |
496 | the timer, and again will automatically restart it if need be. |
502 | the timer, and again will automatically restart it if need be. |
497 | |
503 | |
498 | =back |
504 | =back |
499 | |
505 | |
500 | =head2 C<ev_periodic> - to cron or not to cron it |
506 | =head2 C<ev_periodic> - to cron or not to cron |
501 | |
507 | |
502 | Periodic watchers are also timers of a kind, but they are very versatile |
508 | Periodic watchers are also timers of a kind, but they are very versatile |
503 | (and unfortunately a bit complex). |
509 | (and unfortunately a bit complex). |
504 | |
510 | |
505 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
511 | Unlike C<ev_timer>'s, they are not based on real time (or relative time) |
… | |
… | |
558 | In this mode the values for C<interval> and C<at> are both being |
564 | In this mode the values for C<interval> and C<at> are both being |
559 | ignored. Instead, each time the periodic watcher gets scheduled, the |
565 | ignored. Instead, each time the periodic watcher gets scheduled, the |
560 | reschedule callback will be called with the watcher as first, and the |
566 | reschedule callback will be called with the watcher as first, and the |
561 | current time as second argument. |
567 | current time as second argument. |
562 | |
568 | |
563 | NOTE: I<This callback MUST NOT stop or destroy the periodic or any other |
569 | NOTE: I<This callback MUST NOT stop or destroy any periodic watcher, |
564 | periodic watcher, ever, or make any event loop modifications>. If you need |
570 | ever, or make any event loop modifications>. If you need to stop it, |
565 | to stop it, return C<now + 1e30> (or so, fudge fudge) and stop it afterwards. |
571 | return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by |
566 | |
572 | starting a prepare watcher). |
567 | Also, I<< this callback must always return a time that is later than the |
|
|
568 | passed C<now> value >>. Not even C<now> itself will be ok. |
|
|
569 | |
573 | |
570 | Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
574 | Its prototype is C<ev_tstamp (*reschedule_cb)(struct ev_periodic *w, |
571 | ev_tstamp now)>, e.g.: |
575 | ev_tstamp now)>, e.g.: |
572 | |
576 | |
573 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
577 | static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) |
… | |
… | |
578 | It must return the next time to trigger, based on the passed time value |
582 | It must return the next time to trigger, based on the passed time value |
579 | (that is, the lowest time value larger than to the second argument). It |
583 | (that is, the lowest time value larger than to the second argument). It |
580 | will usually be called just before the callback will be triggered, but |
584 | will usually be called just before the callback will be triggered, but |
581 | might be called at other times, too. |
585 | might be called at other times, too. |
582 | |
586 | |
|
|
587 | NOTE: I<< This callback must always return a time that is later than the |
|
|
588 | passed C<now> value >>. Not even C<now> itself will do, it I<must> be larger. |
|
|
589 | |
583 | This can be used to create very complex timers, such as a timer that |
590 | This can be used to create very complex timers, such as a timer that |
584 | triggers on each midnight, local time. To do this, you would calculate the |
591 | triggers on each midnight, local time. To do this, you would calculate the |
585 | next midnight after C<now> and return the timestamp value for this. How you do this |
592 | next midnight after C<now> and return the timestamp value for this. How |
586 | is, again, up to you (but it is not trivial). |
593 | you do this is, again, up to you (but it is not trivial, which is the main |
|
|
594 | reason I omitted it as an example). |
587 | |
595 | |
588 | =back |
596 | =back |
589 | |
597 | |
590 | =item ev_periodic_again (loop, ev_periodic *) |
598 | =item ev_periodic_again (loop, ev_periodic *) |
591 | |
599 | |
… | |
… | |
601 | Signal watchers will trigger an event when the process receives a specific |
609 | Signal watchers will trigger an event when the process receives a specific |
602 | signal one or more times. Even though signals are very asynchronous, libev |
610 | signal one or more times. Even though signals are very asynchronous, libev |
603 | will try it's best to deliver signals synchronously, i.e. as part of the |
611 | will try it's best to deliver signals synchronously, i.e. as part of the |
604 | normal event processing, like any other event. |
612 | normal event processing, like any other event. |
605 | |
613 | |
606 | You cna configure as many watchers as you like per signal. Only when the |
614 | You can configure as many watchers as you like per signal. Only when the |
607 | first watcher gets started will libev actually register a signal watcher |
615 | first watcher gets started will libev actually register a signal watcher |
608 | with the kernel (thus it coexists with your own signal handlers as long |
616 | with the kernel (thus it coexists with your own signal handlers as long |
609 | as you don't register any with libev). Similarly, when the last signal |
617 | as you don't register any with libev). Similarly, when the last signal |
610 | watcher for a signal is stopped libev will reset the signal handler to |
618 | watcher for a signal is stopped libev will reset the signal handler to |
611 | SIG_DFL (regardless of what it was set to before). |
619 | SIG_DFL (regardless of what it was set to before). |
… | |
… | |
633 | =item ev_child_set (ev_child *, int pid) |
641 | =item ev_child_set (ev_child *, int pid) |
634 | |
642 | |
635 | Configures the watcher to wait for status changes of process C<pid> (or |
643 | Configures the watcher to wait for status changes of process C<pid> (or |
636 | I<any> process if C<pid> is specified as C<0>). The callback can look |
644 | I<any> process if C<pid> is specified as C<0>). The callback can look |
637 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
645 | at the C<rstatus> member of the C<ev_child> watcher structure to see |
638 | the status word (use the macros from C<sys/wait.h>). The C<rpid> member |
646 | the status word (use the macros from C<sys/wait.h> and see your systems |
639 | contains the pid of the process causing the status change. |
647 | C<waitpid> documentation). The C<rpid> member contains the pid of the |
|
|
648 | process causing the status change. |
640 | |
649 | |
641 | =back |
650 | =back |
642 | |
651 | |
643 | =head2 C<ev_idle> - when you've got nothing better to do |
652 | =head2 C<ev_idle> - when you've got nothing better to do |
644 | |
653 | |
645 | Idle watchers trigger events when there are no other I/O or timer (or |
654 | Idle watchers trigger events when there are no other events are pending |
646 | periodic) events pending. That is, as long as your process is busy |
655 | (prepare, check and other idle watchers do not count). That is, as long |
647 | handling sockets or timeouts it will not be called. But when your process |
656 | as your process is busy handling sockets or timeouts (or even signals, |
648 | is idle all idle watchers are being called again and again - until |
657 | imagine) it will not be triggered. But when your process is idle all idle |
|
|
658 | watchers are being called again and again, once per event loop iteration - |
649 | stopped, that is, or your process receives more events. |
659 | until stopped, that is, or your process receives more events and becomes |
|
|
660 | busy. |
650 | |
661 | |
651 | The most noteworthy effect is that as long as any idle watchers are |
662 | The most noteworthy effect is that as long as any idle watchers are |
652 | active, the process will not block when waiting for new events. |
663 | active, the process will not block when waiting for new events. |
653 | |
664 | |
654 | Apart from keeping your process non-blocking (which is a useful |
665 | Apart from keeping your process non-blocking (which is a useful |
… | |
… | |
664 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
675 | kind. There is a C<ev_idle_set> macro, but using it is utterly pointless, |
665 | believe me. |
676 | believe me. |
666 | |
677 | |
667 | =back |
678 | =back |
668 | |
679 | |
669 | =head2 prepare and check - your hooks into the event loop |
680 | =head2 C<ev_prepare> and C<ev_check> - customise your event loop |
670 | |
681 | |
671 | Prepare and check watchers usually (but not always) are used in |
682 | Prepare and check watchers are usually (but not always) used in tandem: |
672 | tandom. Prepare watchers get invoked before the process blocks and check |
683 | prepare watchers get invoked before the process blocks and check watchers |
673 | watchers afterwards. |
684 | afterwards. |
674 | |
685 | |
675 | Their main purpose is to integrate other event mechanisms into libev. This |
686 | Their main purpose is to integrate other event mechanisms into libev. This |
676 | could be used, for example, to track variable changes, implement your own |
687 | could be used, for example, to track variable changes, implement your own |
677 | watchers, integrate net-snmp or a coroutine library and lots more. |
688 | watchers, integrate net-snmp or a coroutine library and lots more. |
678 | |
689 | |
679 | This is done by examining in each prepare call which file descriptors need |
690 | This is done by examining in each prepare call which file descriptors need |
680 | to be watched by the other library, registering C<ev_io> watchers for them |
691 | to be watched by the other library, registering C<ev_io> watchers for |
681 | and starting an C<ev_timer> watcher for any timeouts (many libraries provide |
692 | them and starting an C<ev_timer> watcher for any timeouts (many libraries |
682 | just this functionality). Then, in the check watcher you check for any |
693 | provide just this functionality). Then, in the check watcher you check for |
683 | events that occured (by making your callbacks set soem flags for example) |
694 | any events that occured (by checking the pending status of all watchers |
684 | and call back into the library. |
695 | and stopping them) and call back into the library. The I/O and timer |
|
|
696 | callbacks will never actually be called (but must be valid nevertheless, |
|
|
697 | because you never know, you know?). |
685 | |
698 | |
686 | As another example, the perl Coro module uses these hooks to integrate |
699 | As another example, the Perl Coro module uses these hooks to integrate |
687 | coroutines into libev programs, by yielding to other active coroutines |
700 | coroutines into libev programs, by yielding to other active coroutines |
688 | during each prepare and only letting the process block if no coroutines |
701 | during each prepare and only letting the process block if no coroutines |
689 | are ready to run. |
702 | are ready to run (it's actually more complicated: it only runs coroutines |
|
|
703 | with priority higher than or equal to the event loop and one coroutine |
|
|
704 | of lower priority, but only once, using idle watchers to keep the event |
|
|
705 | loop from blocking if lower-priority coroutines are active, thus mapping |
|
|
706 | low-priority coroutines to idle/background tasks). |
690 | |
707 | |
691 | =over 4 |
708 | =over 4 |
692 | |
709 | |
693 | =item ev_prepare_init (ev_prepare *, callback) |
710 | =item ev_prepare_init (ev_prepare *, callback) |
694 | |
711 | |
695 | =item ev_check_init (ev_check *, callback) |
712 | =item ev_check_init (ev_check *, callback) |
696 | |
713 | |
697 | Initialises and configures the prepare or check watcher - they have no |
714 | Initialises and configures the prepare or check watcher - they have no |
698 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
715 | parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set> |
699 | macros, but using them is utterly, utterly pointless. |
716 | macros, but using them is utterly, utterly and completely pointless. |
700 | |
717 | |
701 | =back |
718 | =back |
702 | |
719 | |
703 | =head1 OTHER FUNCTIONS |
720 | =head1 OTHER FUNCTIONS |
704 | |
721 | |
705 | There are some other fucntions of possible interest. Described. Here. Now. |
722 | There are some other functions of possible interest. Described. Here. Now. |
706 | |
723 | |
707 | =over 4 |
724 | =over 4 |
708 | |
725 | |
709 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
726 | =item ev_once (loop, int fd, int events, ev_tstamp timeout, callback) |
710 | |
727 | |
711 | This function combines a simple timer and an I/O watcher, calls your |
728 | This function combines a simple timer and an I/O watcher, calls your |
712 | callback on whichever event happens first and automatically stop both |
729 | callback on whichever event happens first and automatically stop both |
713 | watchers. This is useful if you want to wait for a single event on an fd |
730 | watchers. This is useful if you want to wait for a single event on an fd |
714 | or timeout without havign to allocate/configure/start/stop/free one or |
731 | or timeout without having to allocate/configure/start/stop/free one or |
715 | more watchers yourself. |
732 | more watchers yourself. |
716 | |
733 | |
717 | If C<fd> is less than 0, then no I/O watcher will be started and events is |
734 | If C<fd> is less than 0, then no I/O watcher will be started and events |
718 | ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and C<events> set |
735 | is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and |
719 | will be craeted and started. |
736 | C<events> set will be craeted and started. |
720 | |
737 | |
721 | If C<timeout> is less than 0, then no timeout watcher will be |
738 | If C<timeout> is less than 0, then no timeout watcher will be |
722 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and repeat |
739 | started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and |
723 | = 0) will be started. |
740 | repeat = 0) will be started. While C<0> is a valid timeout, it is of |
|
|
741 | dubious value. |
724 | |
742 | |
725 | The callback has the type C<void (*cb)(int revents, void *arg)> and |
743 | The callback has the type C<void (*cb)(int revents, void *arg)> and gets |
726 | gets passed an events set (normally a combination of C<EV_ERROR>, C<EV_READ>, |
744 | passed an C<revents> set like normal event callbacks (a combination of |
727 | C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> value passed to C<ev_once>: |
745 | C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg> |
|
|
746 | value passed to C<ev_once>: |
728 | |
747 | |
729 | static void stdin_ready (int revents, void *arg) |
748 | static void stdin_ready (int revents, void *arg) |
730 | { |
749 | { |
731 | if (revents & EV_TIMEOUT) |
750 | if (revents & EV_TIMEOUT) |
732 | /* doh, nothing entered */ |
751 | /* doh, nothing entered */; |
733 | else if (revents & EV_READ) |
752 | else if (revents & EV_READ) |
734 | /* stdin might have data for us, joy! */ |
753 | /* stdin might have data for us, joy! */; |
735 | } |
754 | } |
736 | |
755 | |
737 | ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0); |
756 | ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0); |
738 | |
757 | |
739 | =item ev_feed_event (loop, watcher, int events) |
758 | =item ev_feed_event (loop, watcher, int events) |
740 | |
759 | |
741 | Feeds the given event set into the event loop, as if the specified event |
760 | Feeds the given event set into the event loop, as if the specified event |
742 | has happened for the specified watcher (which must be a pointer to an |
761 | had happened for the specified watcher (which must be a pointer to an |
743 | initialised but not necessarily active event watcher). |
762 | initialised but not necessarily started event watcher). |
744 | |
763 | |
745 | =item ev_feed_fd_event (loop, int fd, int revents) |
764 | =item ev_feed_fd_event (loop, int fd, int revents) |
746 | |
765 | |
747 | Feed an event on the given fd, as if a file descriptor backend detected it. |
766 | Feed an event on the given fd, as if a file descriptor backend detected |
|
|
767 | the given events it. |
748 | |
768 | |
749 | =item ev_feed_signal_event (loop, int signum) |
769 | =item ev_feed_signal_event (loop, int signum) |
750 | |
770 | |
751 | Feed an event as if the given signal occured (loop must be the default loop!). |
771 | Feed an event as if the given signal occured (loop must be the default loop!). |
752 | |
772 | |
753 | =back |
773 | =back |
754 | |
774 | |
|
|
775 | =head1 LIBEVENT EMULATION |
|
|
776 | |
|
|
777 | TBD. |
|
|
778 | |
|
|
779 | =head1 C++ SUPPORT |
|
|
780 | |
|
|
781 | TBD. |
|
|
782 | |
755 | =head1 AUTHOR |
783 | =head1 AUTHOR |
756 | |
784 | |
757 | Marc Lehmann <libev@schmorp.de>. |
785 | Marc Lehmann <libev@schmorp.de>. |
758 | |
786 | |