… | |
… | |
35 | warn "sigquit received\n"; |
35 | warn "sigquit received\n"; |
36 | }; |
36 | }; |
37 | |
37 | |
38 | # CHILD/PID STATUS CHANGES |
38 | # CHILD/PID STATUS CHANGES |
39 | |
39 | |
40 | my $w = EV::child 666, sub { |
40 | my $w = EV::child 666, 0, sub { |
41 | my ($w, $revents) = @_; |
41 | my ($w, $revents) = @_; |
42 | my $status = $w->rstatus; |
42 | my $status = $w->rstatus; |
43 | }; |
43 | }; |
44 | |
44 | |
45 | # STAT CHANGES |
45 | # STAT CHANGES |
… | |
… | |
56 | =head1 DESCRIPTION |
56 | =head1 DESCRIPTION |
57 | |
57 | |
58 | This module provides an interface to libev |
58 | This module provides an interface to libev |
59 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
59 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
60 | below is comprehensive, one might also consult the documentation of libev |
60 | below is comprehensive, one might also consult the documentation of libev |
61 | itself (L<http://cvs.schmorp.de/libev/ev.html>) for more subtle details on |
61 | itself (L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod>) for more |
62 | watcher semantics or some discussion on the available backends, or how to |
62 | subtle details on watcher semantics or some discussion on the available |
63 | force a specific backend with C<LIBEV_FLAGS>, or just about in any case |
63 | backends, or how to force a specific backend with C<LIBEV_FLAGS>, or just |
64 | because it has much more detailed information. |
64 | about in any case because it has much more detailed information. |
|
|
65 | |
|
|
66 | This module is very fast and scalable. It is actually so fast that you |
|
|
67 | can use it through the L<AnyEvent> module, stay portable to other event |
|
|
68 | loops (if you don't rely on any watcher types not available through it) |
|
|
69 | and still be faster than with any other event loop currently supported in |
|
|
70 | Perl. |
65 | |
71 | |
66 | =cut |
72 | =cut |
67 | |
73 | |
68 | package EV; |
74 | package EV; |
69 | |
75 | |
70 | use strict; |
76 | use strict; |
71 | |
77 | |
72 | BEGIN { |
78 | BEGIN { |
73 | our $VERSION = '2.0'; |
79 | our $VERSION = '3.4'; |
74 | use XSLoader; |
80 | use XSLoader; |
75 | XSLoader::load "EV", $VERSION; |
81 | XSLoader::load "EV", $VERSION; |
76 | } |
82 | } |
77 | |
83 | |
78 | @EV::IO::ISA = |
84 | @EV::IO::ISA = |
… | |
… | |
84 | @EV::Idle::ISA = |
90 | @EV::Idle::ISA = |
85 | @EV::Prepare::ISA = |
91 | @EV::Prepare::ISA = |
86 | @EV::Check::ISA = |
92 | @EV::Check::ISA = |
87 | @EV::Embed::ISA = |
93 | @EV::Embed::ISA = |
88 | @EV::Fork::ISA = |
94 | @EV::Fork::ISA = |
|
|
95 | @EV::Async::ISA = |
89 | "EV::Watcher"; |
96 | "EV::Watcher"; |
90 | |
97 | |
91 | @EV::Loop::Default::ISA = "EV::Loop"; |
98 | @EV::Loop::Default::ISA = "EV::Loop"; |
92 | |
99 | |
93 | =head1 EVENT LOOPS |
100 | =head1 EVENT LOOPS |
… | |
… | |
102 | selecting a working backend (which for example rules out kqueue on most |
109 | selecting a working backend (which for example rules out kqueue on most |
103 | BSDs). Modules should, unless they have "special needs" always use the |
110 | BSDs). Modules should, unless they have "special needs" always use the |
104 | default loop as this is fastest (perl-wise), best supported by other |
111 | default loop as this is fastest (perl-wise), best supported by other |
105 | modules (e.g. AnyEvent or Coro) and most portable event loop. |
112 | modules (e.g. AnyEvent or Coro) and most portable event loop. |
106 | |
113 | |
107 | For specific programs you cna create additional event loops dynamically. |
114 | For specific programs you can create additional event loops dynamically. |
108 | |
115 | |
109 | =over 4 |
116 | =over 4 |
110 | |
117 | |
111 | =item $loop = new EV::loop [$flags] |
118 | =item $loop = new EV::loop [$flags] |
112 | |
119 | |
… | |
… | |
126 | Must be called after a fork in the child, before entering or continuing |
133 | Must be called after a fork in the child, before entering or continuing |
127 | the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls |
134 | the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls |
128 | this fucntion automatically, at some performance loss (refer to the libev |
135 | this fucntion automatically, at some performance loss (refer to the libev |
129 | documentation). |
136 | documentation). |
130 | |
137 | |
|
|
138 | =item $loop = EV::default_loop [$flags] |
|
|
139 | |
|
|
140 | Return the default loop (which is a singleton object). |
|
|
141 | |
131 | =back |
142 | =back |
132 | |
143 | |
133 | |
144 | |
134 | =head1 BASIC INTERFACE |
145 | =head1 BASIC INTERFACE |
135 | |
146 | |
… | |
… | |
140 | Must contain a reference to a function that is called when a callback |
151 | Must contain a reference to a function that is called when a callback |
141 | throws an exception (with $@ containing the error). The default prints an |
152 | throws an exception (with $@ containing the error). The default prints an |
142 | informative message and continues. |
153 | informative message and continues. |
143 | |
154 | |
144 | If this callback throws an exception it will be silently ignored. |
155 | If this callback throws an exception it will be silently ignored. |
|
|
156 | |
|
|
157 | =item $flags = EV::supported_backends |
|
|
158 | |
|
|
159 | =item $flags = EV::recommended_backends |
|
|
160 | |
|
|
161 | =item $flags = EV::embeddable_backends |
|
|
162 | |
|
|
163 | Returns the set (see C<EV::BACKEND_*> flags) of backends supported by this |
|
|
164 | instance of EV, the set of recommended backends (supposed to be good) for |
|
|
165 | this platform and the set of embeddable backends (see EMBED WATCHERS). |
|
|
166 | |
|
|
167 | =item EV::sleep $seconds |
|
|
168 | |
|
|
169 | Block the process for the given number of (fractional) seconds. |
145 | |
170 | |
146 | =item $time = EV::time |
171 | =item $time = EV::time |
147 | |
172 | |
148 | Returns the current time in (fractional) seconds since the epoch. |
173 | Returns the current time in (fractional) seconds since the epoch. |
149 | |
174 | |
… | |
… | |
208 | If timeout is C<undef> or negative, then there will be no |
233 | If timeout is C<undef> or negative, then there will be no |
209 | timeout. Otherwise a EV::timer with this value will be started. |
234 | timeout. Otherwise a EV::timer with this value will be started. |
210 | |
235 | |
211 | When an error occurs or either the timeout or I/O watcher triggers, then |
236 | When an error occurs or either the timeout or I/O watcher triggers, then |
212 | the callback will be called with the received event set (in general |
237 | the callback will be called with the received event set (in general |
213 | you can expect it to be a combination of C<EV:ERROR>, C<EV::READ>, |
238 | you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>, |
214 | C<EV::WRITE> and C<EV::TIMEOUT>). |
239 | C<EV::WRITE> and C<EV::TIMEOUT>). |
215 | |
240 | |
216 | EV::once doesn't return anything: the watchers stay active till either |
241 | EV::once doesn't return anything: the watchers stay active till either |
217 | of them triggers, then they will be stopped and freed, and the callback |
242 | of them triggers, then they will be stopped and freed, and the callback |
218 | invoked. |
243 | invoked. |
… | |
… | |
228 | =item EV::feed_signal_event ($signal) |
253 | =item EV::feed_signal_event ($signal) |
229 | |
254 | |
230 | Feed a signal event into EV. EV will react to this call as if the signal |
255 | Feed a signal event into EV. EV will react to this call as if the signal |
231 | specified by C<$signal> had occured. |
256 | specified by C<$signal> had occured. |
232 | |
257 | |
|
|
258 | =item EV::set_io_collect_interval $time |
|
|
259 | |
|
|
260 | =item $loop->set_io_collect_interval ($time) |
|
|
261 | |
|
|
262 | =item EV::set_timeout_collect_interval $time |
|
|
263 | |
|
|
264 | =item $loop->set_timeout_collect_interval ($time) |
|
|
265 | |
|
|
266 | These advanced functions set the minimum block interval when polling for I/O events and the minimum |
|
|
267 | wait interval for timer events. See the libev documentation at |
|
|
268 | L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP> for |
|
|
269 | a more detailed discussion. |
|
|
270 | |
233 | =back |
271 | =back |
234 | |
272 | |
235 | |
273 | |
236 | =head1 WATCHER OBJECTS |
274 | =head1 WATCHER OBJECTS |
237 | |
275 | |
… | |
… | |
239 | event. For instance, if you want to wait for STDIN to become readable, you |
277 | event. For instance, if you want to wait for STDIN to become readable, you |
240 | would create an EV::io watcher for that: |
278 | would create an EV::io watcher for that: |
241 | |
279 | |
242 | my $watcher = EV::io *STDIN, EV::READ, sub { |
280 | my $watcher = EV::io *STDIN, EV::READ, sub { |
243 | my ($watcher, $revents) = @_; |
281 | my ($watcher, $revents) = @_; |
244 | warn "yeah, STDIN should not be readable without blocking!\n" |
282 | warn "yeah, STDIN should now be readable without blocking!\n" |
245 | }; |
283 | }; |
246 | |
284 | |
247 | All watchers can be active (waiting for events) or inactive (paused). Only |
285 | All watchers can be active (waiting for events) or inactive (paused). Only |
248 | active watchers will have their callbacks invoked. All callbacks will be |
286 | active watchers will have their callbacks invoked. All callbacks will be |
249 | called with at least two arguments: the watcher and a bitmask of received |
287 | called with at least two arguments: the watcher and a bitmask of received |
… | |
… | |
333 | Feed some events on this watcher into EV. EV will react to this call as if |
371 | Feed some events on this watcher into EV. EV will react to this call as if |
334 | the watcher had received the given C<$revents> mask. |
372 | the watcher had received the given C<$revents> mask. |
335 | |
373 | |
336 | =item $revents = $w->clear_pending |
374 | =item $revents = $w->clear_pending |
337 | |
375 | |
338 | If the watcher is pending, this function returns clears its pending status |
376 | If the watcher is pending, this function clears its pending status and |
339 | and returns its C<$revents> bitset (as if its callback was invoked). If the |
377 | returns its C<$revents> bitset (as if its callback was invoked). If the |
340 | watcher isn't pending it does nothing and returns C<0>. |
378 | watcher isn't pending it does nothing and returns C<0>. |
341 | |
379 | |
342 | =item $previous_state = $w->keepalive ($bool) |
380 | =item $previous_state = $w->keepalive ($bool) |
343 | |
381 | |
344 | Normally, C<EV::loop> will return when there are no active watchers |
382 | Normally, C<EV::loop> will return when there are no active watchers |
345 | (which is a "deadlock" because no progress can be made anymore). This is |
383 | (which is a "deadlock" because no progress can be made anymore). This is |
346 | convinient because it allows you to start your watchers (and your jobs), |
384 | convinient because it allows you to start your watchers (and your jobs), |
347 | call C<EV::loop> once and when it returns you know that all your jobs are |
385 | call C<EV::loop> once and when it returns you know that all your jobs are |
348 | finished (or they forgot to register some watchers for their task :). |
386 | finished (or they forgot to register some watchers for their task :). |
349 | |
387 | |
350 | Sometimes, however, this gets in your way, for example when you the module |
388 | Sometimes, however, this gets in your way, for example when the module |
351 | that calls C<EV::loop> (usually the main program) is not the same module |
389 | that calls C<EV::loop> (usually the main program) is not the same module |
352 | as a long-living watcher (for example a DNS client module written by |
390 | as a long-living watcher (for example a DNS client module written by |
353 | somebody else even). Then you might want any outstanding requests to be |
391 | somebody else even). Then you might want any outstanding requests to be |
354 | handled, but you would not want to keep C<EV::loop> from returning just |
392 | handled, but you would not want to keep C<EV::loop> from returning just |
355 | because you happen to have this long-running UDP port watcher. |
393 | because you happen to have this long-running UDP port watcher. |
… | |
… | |
384 | |
422 | |
385 | =item $w = EV::io $fileno_or_fh, $eventmask, $callback |
423 | =item $w = EV::io $fileno_or_fh, $eventmask, $callback |
386 | |
424 | |
387 | =item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
425 | =item $w = EV::io_ns $fileno_or_fh, $eventmask, $callback |
388 | |
426 | |
389 | =item $w = $loop->io 8$fileno_or_fh, $eventmask, $callback) |
427 | =item $w = $loop->io ($fileno_or_fh, $eventmask, $callback) |
390 | |
428 | |
391 | =item $w = $loop->io_ns ($fileno_or_fh, $eventmask, $callback) |
429 | =item $w = $loop->io_ns ($fileno_or_fh, $eventmask, $callback) |
392 | |
430 | |
393 | As long as the returned watcher object is alive, call the C<$callback> |
431 | As long as the returned watcher object is alive, call the C<$callback> |
394 | when at least one of events specified in C<$eventmask> occurs. |
432 | when at least one of events specified in C<$eventmask> occurs. |
… | |
… | |
502 | This time simply fires at the wallclock time C<$at> and doesn't repeat. It |
540 | This time simply fires at the wallclock time C<$at> and doesn't repeat. It |
503 | will not adjust when a time jump occurs, that is, if it is to be run |
541 | will not adjust when a time jump occurs, that is, if it is to be run |
504 | at January 1st 2011 then it will run when the system time reaches or |
542 | at January 1st 2011 then it will run when the system time reaches or |
505 | surpasses this time. |
543 | surpasses this time. |
506 | |
544 | |
507 | =item * non-repeating interval timer ($interval > 0, $reschedule_cb = 0) |
545 | =item * repeating interval timer ($interval > 0, $reschedule_cb = 0) |
508 | |
546 | |
509 | In this mode the watcher will always be scheduled to time out at the |
547 | In this mode the watcher will always be scheduled to time out at the |
510 | next C<$at + N * $interval> time (for some integer N) and then repeat, |
548 | next C<$at + N * $interval> time (for some integer N) and then repeat, |
511 | regardless of any time jumps. |
549 | regardless of any time jumps. |
512 | |
550 | |
… | |
… | |
530 | time the periodic watcher gets scheduled, the reschedule callback |
568 | time the periodic watcher gets scheduled, the reschedule callback |
531 | ($reschedule_cb) will be called with the watcher as first, and the current |
569 | ($reschedule_cb) will be called with the watcher as first, and the current |
532 | time as second argument. |
570 | time as second argument. |
533 | |
571 | |
534 | I<This callback MUST NOT stop or destroy this or any other periodic |
572 | I<This callback MUST NOT stop or destroy this or any other periodic |
535 | watcher, ever>. If you need to stop it, return 1e30 and stop it |
573 | watcher, ever, and MUST NOT call any event loop functions or methods>. If |
536 | afterwards. |
574 | you need to stop it, return 1e30 and stop it afterwards. You may create |
|
|
575 | and start a C<EV::prepare> watcher for this task. |
537 | |
576 | |
538 | It must return the next time to trigger, based on the passed time value |
577 | It must return the next time to trigger, based on the passed time value |
539 | (that is, the lowest time value larger than to the second argument). It |
578 | (that is, the lowest time value larger than or equal to to the second |
540 | will usually be called just before the callback will be triggered, but |
579 | argument). It will usually be called just before the callback will be |
541 | might be called at other times, too. |
580 | triggered, but might be called at other times, too. |
542 | |
581 | |
543 | This can be used to create very complex timers, such as a timer that |
582 | This can be used to create very complex timers, such as a timer that |
544 | triggers on each midnight, local time (actually 24 hours after the last |
583 | triggers on each midnight, local time (actually 24 hours after the last |
545 | midnight, to keep the example simple. If you know a way to do it correctly |
584 | midnight, to keep the example simple. If you know a way to do it correctly |
546 | in about the same space (without requiring elaborate modules), drop me a |
585 | in about the same space (without requiring elaborate modules), drop me a |
… | |
… | |
613 | |
652 | |
614 | =head3 CHILD WATCHERS - watch out for process status changes |
653 | =head3 CHILD WATCHERS - watch out for process status changes |
615 | |
654 | |
616 | =over 4 |
655 | =over 4 |
617 | |
656 | |
618 | =item $w = EV::child $pid, $callback |
657 | =item $w = EV::child $pid, $trace, $callback |
619 | |
658 | |
620 | =item $w = EV::child_ns $pid, $callback |
659 | =item $w = EV::child_ns $pid, $trace, $callback |
621 | |
660 | |
622 | =item $w = $loop->child ($pid, $callback) |
661 | =item $w = $loop->child ($pid, $trace, $callback) |
623 | |
662 | |
624 | =item $w = $loop->child_ns ($pid, $callback) |
663 | =item $w = $loop->child_ns ($pid, $trace, $callback) |
625 | |
664 | |
626 | Call the callback when a status change for pid C<$pid> (or any pid if |
665 | Call the callback when a status change for pid C<$pid> (or any pid |
627 | C<$pid> is 0) has been received. More precisely: when the process receives |
666 | if C<$pid> is 0) has been received (a status change happens when the |
|
|
667 | process terminates or is killed, or, when trace is true, additionally when |
|
|
668 | it is stopped or continued). More precisely: when the process receives |
628 | a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all |
669 | a C<SIGCHLD>, EV will fetch the outstanding exit/wait status for all |
629 | changed/zombie children and call the callback. |
670 | changed/zombie children and call the callback. |
630 | |
671 | |
631 | It is valid (and fully supported) to install a child watcher after a child |
672 | It is valid (and fully supported) to install a child watcher after a child |
632 | has exited but before the event loop has started its next iteration (for |
673 | has exited but before the event loop has started its next iteration (for |
… | |
… | |
639 | You can have as many pid watchers per pid as you want, they will all be |
680 | You can have as many pid watchers per pid as you want, they will all be |
640 | called. |
681 | called. |
641 | |
682 | |
642 | The C<child_ns> variant doesn't start (activate) the newly created watcher. |
683 | The C<child_ns> variant doesn't start (activate) the newly created watcher. |
643 | |
684 | |
644 | =item $w->set ($pid) |
685 | =item $w->set ($pid, $trace) |
645 | |
686 | |
646 | Reconfigures the watcher, see the constructor above for details. Can be called at |
687 | Reconfigures the watcher, see the constructor above for details. Can be called at |
647 | any time. |
688 | any time. |
648 | |
689 | |
649 | =item $current_pid = $w->pid |
690 | =item $current_pid = $w->pid |
650 | |
|
|
651 | =item $old_pid = $w->pid ($new_pid) |
|
|
652 | |
691 | |
653 | Returns the previously set process id and optionally set a new one. |
692 | Returns the previously set process id and optionally set a new one. |
654 | |
693 | |
655 | =item $exit_status = $w->rstatus |
694 | =item $exit_status = $w->rstatus |
656 | |
695 | |
… | |
… | |
791 | |
830 | |
792 | =item $w = EV::prepare_ns $callback |
831 | =item $w = EV::prepare_ns $callback |
793 | |
832 | |
794 | =item $w = $loop->prepare ($callback) |
833 | =item $w = $loop->prepare ($callback) |
795 | |
834 | |
796 | =item $w = $loop->prepare_ns 8$callback) |
835 | =item $w = $loop->prepare_ns ($callback) |
797 | |
836 | |
798 | Call the callback just before the process would block. You can still |
837 | Call the callback just before the process would block. You can still |
799 | create/modify any watchers at this point. |
838 | create/modify any watchers at this point. |
800 | |
839 | |
801 | See the EV::check watcher, below, for explanations and an example. |
840 | See the EV::check watcher, below, for explanations and an example. |
… | |
… | |
890 | The C<fork_ns> variant doesn't start (activate) the newly created watcher. |
929 | The C<fork_ns> variant doesn't start (activate) the newly created watcher. |
891 | |
930 | |
892 | =back |
931 | =back |
893 | |
932 | |
894 | |
933 | |
|
|
934 | =head3 EMBED WATCHERS - when one backend isn't enough... |
|
|
935 | |
|
|
936 | This is a rather advanced watcher type that lets you embed one event loop |
|
|
937 | into another (currently only IO events are supported in the embedded |
|
|
938 | loop, other types of watchers might be handled in a delayed or incorrect |
|
|
939 | fashion and must not be used). |
|
|
940 | |
|
|
941 | See the libev documentation at |
|
|
942 | L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#code_ev_embed_code_when_one_backend_> |
|
|
943 | for more details. |
|
|
944 | |
|
|
945 | In short, this watcher is most useful on BSD systems without working |
|
|
946 | kqueue to still be able to handle a large number of sockets: |
|
|
947 | |
|
|
948 | my $socket_loop; |
|
|
949 | |
|
|
950 | # check wether we use SELECT or POLL _and_ KQUEUE is supported |
|
|
951 | if ( |
|
|
952 | (EV::backend & (EV::BACKEND_POLL | EV::BACKEND_SELECT)) |
|
|
953 | && (EV::supported_backends & EV::embeddable_backends & EV::BACKEND_KQUEUE) |
|
|
954 | ) { |
|
|
955 | # use kqueue for sockets |
|
|
956 | $socket_loop = new EV::Loop EV::BACKEND_KQUEUE | EV::FLAG_NOENV; |
|
|
957 | } |
|
|
958 | |
|
|
959 | # use the default loop otherwise |
|
|
960 | $socket_loop ||= EV::default_loop; |
|
|
961 | |
|
|
962 | =over 4 |
|
|
963 | |
|
|
964 | =item $w = EV::embed $otherloop, $callback |
|
|
965 | |
|
|
966 | =item $w = EV::embed_ns $otherloop, $callback |
|
|
967 | |
|
|
968 | =item $w = $loop->embed ($otherloop, $callback) |
|
|
969 | |
|
|
970 | =item $w = $loop->embed_ns ($otherloop, $callback) |
|
|
971 | |
|
|
972 | Call the callback when the embedded event loop (C<$otherloop>) has any |
|
|
973 | I/O activity. The C<$callback> should alwas be specified as C<undef> in |
|
|
974 | this version of EV, which means the embedded event loop will be managed |
|
|
975 | automatically. |
|
|
976 | |
|
|
977 | The C<embed_ns> variant doesn't start (activate) the newly created watcher. |
|
|
978 | |
|
|
979 | =back |
|
|
980 | |
|
|
981 | =head3 ASYNC WATCHERS - how to wake up another event loop |
|
|
982 | |
|
|
983 | Async watchers are provided by EV, but have little use in perl directly, as perl |
|
|
984 | neither supports threads nor direct access to signal handlers or other |
|
|
985 | contexts where they could be of value. |
|
|
986 | |
|
|
987 | It is, however, possible to use them from the XS level. |
|
|
988 | |
|
|
989 | Please see the libev documentation for further details. |
|
|
990 | |
|
|
991 | =over 4 |
|
|
992 | |
|
|
993 | =item $w = EV::async $callback |
|
|
994 | |
|
|
995 | =item $w = EV::async_ns $callback |
|
|
996 | |
|
|
997 | =item $w->send |
|
|
998 | |
|
|
999 | =item $bool = $w->async_pending |
|
|
1000 | |
|
|
1001 | =back |
|
|
1002 | |
|
|
1003 | |
895 | =head1 PERL SIGNALS |
1004 | =head1 PERL SIGNALS |
896 | |
1005 | |
897 | While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour |
1006 | While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour |
898 | with EV is as the same as any other C library: Perl-signals will only be |
1007 | with EV is as the same as any other C library: Perl-signals will only be |
899 | handled when Perl runs, which means your signal handler might be invoked |
1008 | handled when Perl runs, which means your signal handler might be invoked |
… | |
… | |
906 | to be called on every event loop iteration by installing a C<EV::check> |
1015 | to be called on every event loop iteration by installing a C<EV::check> |
907 | watcher: |
1016 | watcher: |
908 | |
1017 | |
909 | my $async_check = EV::check sub { }; |
1018 | my $async_check = EV::check sub { }; |
910 | |
1019 | |
911 | This ensures that perl shortly gets into control for a short time, and |
1020 | This ensures that perl gets into control for a short time to handle any |
912 | also ensures slower overall operation. |
1021 | pending signals, and also ensures (slightly) slower overall operation. |
913 | |
1022 | |
914 | =head1 THREADS |
1023 | =head1 THREADS |
915 | |
1024 | |
916 | Threads are not supported by this module in any way. Perl pseudo-threads |
1025 | Threads are not supported by this module in any way. Perl pseudo-threads |
917 | is evil stuff and must die. As soon as Perl gains real threads I will work |
1026 | is evil stuff and must die. As soon as Perl gains real threads I will work |
… | |
… | |
947 | |
1056 | |
948 | =head1 SEE ALSO |
1057 | =head1 SEE ALSO |
949 | |
1058 | |
950 | L<EV::ADNS> (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as |
1059 | L<EV::ADNS> (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as |
951 | event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient |
1060 | event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient |
952 | coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP). |
1061 | coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for |
|
|
1062 | event-loop agnostic and portable event driven programming. |
953 | |
1063 | |
954 | =head1 AUTHOR |
1064 | =head1 AUTHOR |
955 | |
1065 | |
956 | Marc Lehmann <schmorp@schmorp.de> |
1066 | Marc Lehmann <schmorp@schmorp.de> |
957 | http://home.schmorp.de/ |
1067 | http://home.schmorp.de/ |