… | |
… | |
51 | # MAINLOOP |
51 | # MAINLOOP |
52 | EV::loop; # loop until EV::unloop is called or all watchers stop |
52 | EV::loop; # loop until EV::unloop is called or all watchers stop |
53 | EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled |
53 | EV::loop EV::LOOP_ONESHOT; # block until at least one event could be handled |
54 | EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
54 | EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block |
55 | |
55 | |
|
|
56 | =head1 BEFORE YOU START USING THIS MODULE |
|
|
57 | |
|
|
58 | If you only need timer, I/O, signal, child and idle watchers and not the |
|
|
59 | advanced functionality of this module, consider using L<AnyEvent> instead, |
|
|
60 | specifically the simplified API described in L<AE>. |
|
|
61 | |
|
|
62 | When used with EV as backend, the L<AE> API is as fast as the native L<EV> |
|
|
63 | API, but your programs/modules will still run with many other event loops. |
|
|
64 | |
56 | =head1 DESCRIPTION |
65 | =head1 DESCRIPTION |
57 | |
66 | |
58 | This module provides an interface to libev |
67 | This module provides an interface to libev |
59 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
68 | (L<http://software.schmorp.de/pkg/libev.html>). While the documentation |
60 | below is comprehensive, one might also consult the documentation of |
69 | below is comprehensive, one might also consult the documentation of |
… | |
… | |
79 | package EV; |
88 | package EV; |
80 | |
89 | |
81 | use common::sense; |
90 | use common::sense; |
82 | |
91 | |
83 | BEGIN { |
92 | BEGIN { |
84 | our $VERSION = '3.8'; |
93 | our $VERSION = '4.00'; |
85 | use XSLoader; |
94 | use XSLoader; |
86 | XSLoader::load "EV", $VERSION; |
95 | XSLoader::load "EV", $VERSION; |
87 | } |
96 | } |
88 | |
97 | |
89 | @EV::IO::ISA = |
98 | @EV::IO::ISA = |
… | |
… | |
299 | timeout. Otherwise a EV::timer with this value will be started. |
308 | timeout. Otherwise a EV::timer with this value will be started. |
300 | |
309 | |
301 | When an error occurs or either the timeout or I/O watcher triggers, then |
310 | When an error occurs or either the timeout or I/O watcher triggers, then |
302 | the callback will be called with the received event set (in general |
311 | the callback will be called with the received event set (in general |
303 | you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>, |
312 | you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>, |
304 | C<EV::WRITE> and C<EV::TIMEOUT>). |
313 | C<EV::WRITE> and C<EV::TIMER>). |
305 | |
314 | |
306 | EV::once doesn't return anything: the watchers stay active till either |
315 | EV::once doesn't return anything: the watchers stay active till either |
307 | of them triggers, then they will be stopped and freed, and the callback |
316 | of them triggers, then they will be stopped and freed, and the callback |
308 | invoked. |
317 | invoked. |
309 | |
318 | |
… | |
… | |
366 | |
375 | |
367 | Each watcher type has its associated bit in revents, so you can use the |
376 | Each watcher type has its associated bit in revents, so you can use the |
368 | same callback for multiple watchers. The event mask is named after the |
377 | same callback for multiple watchers. The event mask is named after the |
369 | type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
378 | type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE, |
370 | EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events |
379 | EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events |
371 | (which can set both EV::READ and EV::WRITE bits), and EV::timer (which |
380 | (which can set both EV::READ and EV::WRITE bits). |
372 | uses EV::TIMEOUT). |
|
|
373 | |
381 | |
374 | In the rare case where one wants to create a watcher but not start it at |
382 | In the rare case where one wants to create a watcher but not start it at |
375 | the same time, each constructor has a variant with a trailing C<_ns> in |
383 | the same time, each constructor has a variant with a trailing C<_ns> in |
376 | its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. |
384 | its name, e.g. EV::io has a non-starting variant EV::io_ns and so on. |
377 | |
385 | |
… | |
… | |
456 | |
464 | |
457 | =item $previous_state = $w->keepalive ($bool) |
465 | =item $previous_state = $w->keepalive ($bool) |
458 | |
466 | |
459 | Normally, C<EV::loop> will return when there are no active watchers |
467 | Normally, C<EV::loop> will return when there are no active watchers |
460 | (which is a "deadlock" because no progress can be made anymore). This is |
468 | (which is a "deadlock" because no progress can be made anymore). This is |
461 | convinient because it allows you to start your watchers (and your jobs), |
469 | convenient because it allows you to start your watchers (and your jobs), |
462 | call C<EV::loop> once and when it returns you know that all your jobs are |
470 | call C<EV::loop> once and when it returns you know that all your jobs are |
463 | finished (or they forgot to register some watchers for their task :). |
471 | finished (or they forgot to register some watchers for their task :). |
464 | |
472 | |
465 | Sometimes, however, this gets in your way, for example when the module |
473 | Sometimes, however, this gets in your way, for example when the module |
466 | that calls C<EV::loop> (usually the main program) is not the same module |
474 | that calls C<EV::loop> (usually the main program) is not the same module |
… | |
… | |
698 | |
706 | |
699 | =item $w = EV::signal $signal, $callback |
707 | =item $w = EV::signal $signal, $callback |
700 | |
708 | |
701 | =item $w = EV::signal_ns $signal, $callback |
709 | =item $w = EV::signal_ns $signal, $callback |
702 | |
710 | |
|
|
711 | =item $w = $loop->signal ($signal, $callback) |
|
|
712 | |
|
|
713 | =item $w = $loop->signal_ns ($signal, $callback) |
|
|
714 | |
703 | Call the callback when $signal is received (the signal can be specified by |
715 | Call the callback when $signal is received (the signal can be specified by |
704 | number or by name, just as with C<kill> or C<%SIG>). |
716 | number or by name, just as with C<kill> or C<%SIG>). |
|
|
717 | |
|
|
718 | Only one event loop can grab a given signal - attempting to grab the same |
|
|
719 | signal from two EV loops will crash the program immediately or cause data |
|
|
720 | corruption. |
705 | |
721 | |
706 | EV will grab the signal for the process (the kernel only allows one |
722 | EV will grab the signal for the process (the kernel only allows one |
707 | component to receive a signal at a time) when you start a signal watcher, |
723 | component to receive a signal at a time) when you start a signal watcher, |
708 | and removes it again when you stop it. Perl does the same when you |
724 | and removes it again when you stop it. Perl does the same when you |
709 | add/remove callbacks to C<%SIG>, so watch out. |
725 | add/remove callbacks to C<%SIG>, so watch out. |