ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/EV/EV.pm
(Generate patch)

Comparing EV/EV.pm (file contents):
Revision 1.126 by root, Tue Mar 16 17:11:48 2010 UTC vs.
Revision 1.128 by root, Thu Oct 21 02:46:59 2010 UTC

… …
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
58If you only need timer, I/O, signal, child and idle watchers and not the
59advanced functionality of this module, consider using L<AnyEvent> instead,
60specifically the simplified API described in L<AE>.
61
62When used with EV as backend, the L<AE> API is as fast as the native L<EV>
63API, but your programs/modules will still run with many other event loops.
64
56=head1 DESCRIPTION 65=head1 DESCRIPTION
57 66
58This module provides an interface to libev 67This 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
60below is comprehensive, one might also consult the documentation of 69below is comprehensive, one might also consult the documentation of
… …
941=item $w = $loop->check_ns ($callback) 950=item $w = $loop->check_ns ($callback)
942 951
943Call the callback just after the process wakes up again (after it has 952Call the callback just after the process wakes up again (after it has
944gathered events), but before any other callbacks have been invoked. 953gathered events), but before any other callbacks have been invoked.
945 954
946This is used to integrate other event-based software into the EV 955This can be used to integrate other event-based software into the EV
947mainloop: You register a prepare callback and in there, you create io and 956mainloop: You register a prepare callback and in there, you create io and
948timer watchers as required by the other software. Here is a real-world 957timer watchers as required by the other software. Here is a real-world
949example of integrating Net::SNMP (with some details left out): 958example of integrating Net::SNMP (with some details left out):
950 959
951 our @snmp_watcher; 960 our @snmp_watcher;
… …
985The callbacks of the created watchers will not be called as the watchers 994The callbacks of the created watchers will not be called as the watchers
986are destroyed before this can happen (remember EV::check gets called 995are destroyed before this can happen (remember EV::check gets called
987first). 996first).
988 997
989The C<check_ns> variant doesn't start (activate) the newly created watcher. 998The C<check_ns> variant doesn't start (activate) the newly created watcher.
999
1000=item EV::CHECK constant issues
1001
1002Like all other watcher types, there is a bitmask constant for use in
1003C<$revents> and other places. The C<EV::CHECK> is special as it has
1004the same name as the C<CHECK> sub called by Perl. This doesn't cause
1005big issues on newer perls (beginning with 5.8.9), but it means thatthe
1006constant must be I<inlined>, i.e. runtime calls will not work. That means
1007that as long as you always C<use EV> and then C<EV::CHECK> you are on the
1008safe side.
990 1009
991=back 1010=back
992 1011
993 1012
994=head3 FORK WATCHERS - the audacity to resume the event loop after a fork 1013=head3 FORK WATCHERS - the audacity to resume the event loop after a fork

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines