[ViewVC] Diff of: cvs/EV/EV.pm

Comparing EV/EV.pm (file contents):
Revision 1.117 by root, Tue Jul 14 00:09:59 2009 UTC vs.
Revision 1.151 by root, Tue Sep 4 23:14:45 2018 UTC

       my ($w, $revents) = @_;
       warn $w->path, " has changed somehow.\n";
    };
    # MAINLOOP
-   EV::loop;           # loop until EV::unloop is called or all watchers stop
+   EV::run;                # loop until EV::break is called or all watchers stop
-   EV::loop EV::LOOP_ONESHOT;  # block until at least one event could be handled
+   EV::run EV::RUN_ONCE;   # block until at least one event could be handled
-   EV::loop EV::LOOP_NONBLOCK; # try to handle same events, but do not block
+   EV::run EV::RUN_NOWAIT; # try to handle same events, but do not block
+=head1 BEFORE YOU START USING THIS MODULE
+If you only need timer, I/O, signal, child and idle watchers and not the
+advanced functionality of this module, consider using L<AnyEvent> instead,
+specifically the simplified API described in L<AE>.
+When used with EV as backend, the L<AE> API is as fast as the native L<EV>
+API, but your programs/modules will still run with many other event loops.
 =head1 DESCRIPTION
 This module provides an interface to libev
 (L<http://software.schmorp.de/pkg/libev.html>). While the documentation
 can use it through the L<AnyEvent> module, stay portable to other event
 loops (if you don't rely on any watcher types not available through it)
 and still be faster than with any other event loop currently supported in
 Perl.
+=head2 PORTING FROM EV 3.X to 4.X
+EV version 4 introduces a number of incompatible changes summarised
+here. According to the depreciation strategy used by libev, there is a
+compatibility layer in place so programs should continue to run unchanged
+(the XS interface lacks this layer, so programs using that one need to be
+updated).
+This compatibility layer will be switched off in some future release.
+All changes relevant to Perl are renames of symbols, functions and
+methods:
+  EV::loop          => EV::run
+  EV::LOOP_NONBLOCK => EV::RUN_NOWAIT
+  EV::LOOP_ONESHOT  => EV::RUN_ONCE
+  EV::unloop        => EV::break
+  EV::UNLOOP_CANCEL => EV::BREAK_CANCEL
+  EV::UNLOOP_ONE    => EV::BREAK_ONE
+  EV::UNLOOP_ALL    => EV::BREAK_ALL
+  EV::TIMEOUT       => EV::TIMER
+  EV::loop_count    => EV::iteration
+  EV::loop_depth    => EV::depth
+  EV::loop_verify   => EV::verify
+The loop object methods corresponding to the functions above have been
+similarly renamed.
 =head2 MODULE EXPORTS
 This module does not export any symbols.
 =cut
 package EV;
 use common::sense;
 BEGIN {
-   our $VERSION = '3.6';
+   our $VERSION = 4.22;
    use XSLoader;
+   local $^W = 0; # avoid spurious warning
    XSLoader::load "EV", $VERSION;
 }
 @EV::IO::ISA       =
 @EV::Timer::ISA    =
 Must be called after a fork in the child, before entering or continuing
 the event loop. An alternative is to use C<EV::FLAG_FORKCHECK> which calls
 this function automatically, at some performance loss (refer to the libev
 documentation).
-=item $loop->loop_verify
+=item $loop->verify
 Calls C<ev_verify> to make internal consistency checks (for debugging
 libev) and abort the program if any data structures were found to be
 corrupted.
 =item $backend = $loop->backend
 Returns an integer describing the backend used by libev (EV::BACKEND_SELECT
 or EV::BACKEND_EPOLL).
-=item EV::loop [$flags]
+=item $active = EV::run [$flags]
-=item $loop->loop ([$flags])
+=item $active = $loop->run ([$flags])
 Begin checking for events and calling callbacks. It returns when a
-callback calls EV::unloop.
+callback calls EV::break or the flags are nonzero (in which case the
+return value is true) or when there are no active watchers which reference
+the loop (keepalive is true), in which case the return value will be
+false. The return value can generally be interpreted as "if true, there is
+more work left to do".
 The $flags argument can be one of the following:
-   0                  as above
+   0               as above
-   EV::LOOP_ONESHOT   block at most once (wait, but do not loop)
+   EV::RUN_ONCE    block at most once (wait, but do not loop)
-   EV::LOOP_NONBLOCK  do not block at all (fetch/handle events but do not wait)
+   EV::RUN_NOWAIT  do not block at all (fetch/handle events but do not wait)
-=item EV::unloop [$how]
+=item EV::break [$how]
-=item $loop->unloop ([$how])
+=item $loop->break ([$how])
-When called with no arguments or an argument of EV::UNLOOP_ONE, makes the
+When called with no arguments or an argument of EV::BREAK_ONE, makes the
 innermost call to EV::loop return.
-When called with an argument of EV::UNLOOP_ALL, all calls to EV::loop will return as
+When called with an argument of EV::BREAK_ALL, all calls to EV::loop will
-fast as possible.
+return as fast as possible.
-=item $count = EV::loop_count
+When called with an argument of EV::BREAK_CANCEL, any pending break will
+be cancelled.
+=item $count = EV::iteration
-=item $count = $loop->loop_count
+=item $count = $loop->iteration
 Return the number of times the event loop has polled for new
 events. Sometimes useful as a generation counter.
 =item EV::once $fh_or_undef, $events, $timeout, $cb->($revents)
 timeout. Otherwise a EV::timer with this value will be started.
 When an error occurs or either the timeout or I/O watcher triggers, then
 the callback will be called with the received event set (in general
 you can expect it to be a combination of C<EV::ERROR>, C<EV::READ>,
-C<EV::WRITE> and C<EV::TIMEOUT>).
+C<EV::WRITE> and C<EV::TIMER>).
 EV::once doesn't return anything: the watchers stay active till either
 of them triggers, then they will be stopped and freed, and the callback
 invoked.
-=item EV::feed_fd_event ($fd, $revents)
+=item EV::feed_fd_event $fd, $revents
 =item $loop->feed_fd_event ($fd, $revents)
 Feed an event on a file descriptor into EV. EV will react to this call as
 if the readyness notifications specified by C<$revents> (a combination of
 C<EV::READ> and C<EV::WRITE>) happened on the file descriptor C<$fd>.
-=item EV::feed_signal_event ($signal)
+=item EV::feed_signal_event $signal
-Feed a signal event into EV. EV will react to this call as if the signal
+Feed a signal event into the default loop. EV will react to this call as
-specified by C<$signal> had occured.
+if the signal specified by C<$signal> had occured.
+=item EV::feed_signal $signal
+Feed a signal event into EV - unlike C<EV::feed_signal_event>, this works
+regardless of which loop has registered the signal, and is mainly useful
+fro custom signal implementations.
 =item EV::set_io_collect_interval $time
 =item $loop->set_io_collect_interval ($time)
 These advanced functions set the minimum block interval when polling for I/O events and the minimum
 wait interval for timer events. See the libev documentation at
 L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#FUNCTIONS_CONTROLLING_THE_EVENT_LOOP>
 (locally installed as F<EV::libev>) for a more detailed discussion.
+=item $count = EV::pending_count
+=item $count = $loop->pending_count
+Returns the number of currently pending watchers.
+=item EV::invoke_pending
+=item $loop->invoke_pending
+Invoke all currently pending watchers.
 =back
 =head1 WATCHER OBJECTS
 Each watcher type has its associated bit in revents, so you can use the
 same callback for multiple watchers. The event mask is named after the
 type, i.e. EV::child sets EV::CHILD, EV::prepare sets EV::PREPARE,
 EV::periodic sets EV::PERIODIC and so on, with the exception of I/O events
-(which can set both EV::READ and EV::WRITE bits), and EV::timer (which
+(which can set both EV::READ and EV::WRITE bits).
-uses EV::TIMEOUT).
 In the rare case where one wants to create a watcher but not start it at
 the same time, each constructor has a variant with a trailing C<_ns> in
 its name, e.g. EV::io has a non-starting variant EV::io_ns and so on.
 =item $previous_state = $w->keepalive ($bool)
 Normally, C<EV::loop> will return when there are no active watchers
 (which is a "deadlock" because no progress can be made anymore). This is
-convinient because it allows you to start your watchers (and your jobs),
+convenient because it allows you to start your watchers (and your jobs),
 call C<EV::loop> once and when it returns you know that all your jobs are
 finished (or they forgot to register some watchers for their task :).
 Sometimes, however, this gets in your way, for example when the module
 that calls C<EV::loop> (usually the main program) is not the same module
 =item $w = $loop->timer ($after, $repeat, $callback)
 =item $w = $loop->timer_ns ($after, $repeat, $callback)
-Calls the callback after C<$after> seconds (which may be fractional). If
+Calls the callback after C<$after> seconds (which may be fractional or
-C<$repeat> is non-zero, the timer will be restarted (with the $repeat
+negative). If C<$repeat> is non-zero, the timer will be restarted (with
-value as $after) after the callback returns.
+the $repeat value as $after) after the callback returns.
 This means that the callback would be called roughly after C<$after>
 seconds, and then every C<$repeat> seconds. The timer does his best not
 to drift, but it will not invoke the timer more often then once per event
 loop iteration, and might drift in other cases. If that isn't acceptable,
 in front of the machine while the timer is running and changes the system
 clock, the timer will nevertheless run (roughly) the same time.
 The C<timer_ns> variant doesn't start (activate) the newly created watcher.
-=item $w->set ($after, $repeat)
+=item $w->set ($after, $repeat = 0)
 Reconfigures the watcher, see the constructor above for details. Can be called at
 any time.
 =item $w->again
+=item $w->again ($repeat)
 Similar to the C<start> method, but has special semantics for repeating timers:
 If the timer is active and non-repeating, it will be stopped.
 This behaviour is useful when you have a timeout for some IO
 operation. You create a timer object with the same value for C<$after> and
 C<$repeat>, and then, in the read/write watcher, run the C<again> method
 on the timeout.
+If called with a C<$repeat> argument, then it uses this a timer repeat
+value.
+=item $after = $w->remaining
+Calculates and returns the remaining time till the timer will fire.
 =back
 =head3 PERIODIC WATCHERS - to cron or not to cron?
 surpasses this time.
 =item * repeating interval timer ($interval > 0, $reschedule_cb = 0)
 In this mode the watcher will always be scheduled to time out at the
-next C<$at + N * $interval> time (for some integer N) and then repeat,
+next C<$at + N * $interval> time (for the lowest integer N) and then repeat,
-regardless of any time jumps.
+regardless of any time jumps. Note that, since C<N> can be negative, the
+first trigger can happen before C<$at>.
 This can be used to create timers that do not drift with respect to system
 time:
    my $hourly = EV::periodic 0, 3600, 0, sub { print "once/hour\n" };
 That doesn't mean there will always be 3600 seconds in between triggers,
-but only that the the clalback will be called when the system time shows a
+but only that the the callback will be called when the system time shows a
 full hour (UTC).
 Another way to think about it (for the mathematically inclined) is that
 EV::periodic will try to run the callback in this mode at the next
 possible time where C<$time = $at (mod $interval)>, regardless of any time
 =item $w = EV::signal $signal, $callback
 =item $w = EV::signal_ns $signal, $callback
+=item $w = $loop->signal ($signal, $callback)
+=item $w = $loop->signal_ns ($signal, $callback)
 Call the callback when $signal is received (the signal can be specified by
 number or by name, just as with C<kill> or C<%SIG>).
+Only one event loop can grab a given signal - attempting to grab the same
+signal from two EV loops will crash the program immediately or cause data
+corruption.
 EV will grab the signal for the process (the kernel only allows one
 component to receive a signal at a time) when you start a signal watcher,
 and removes it again when you stop it. Perl does the same when you
 add/remove callbacks to C<%SIG>, so watch out.
 =item $w = $loop->check_ns ($callback)
 Call the callback just after the process wakes up again (after it has
 gathered events), but before any other callbacks have been invoked.
-This is used to integrate other event-based software into the EV
+This can be used to integrate other event-based software into the EV
 mainloop: You register a prepare callback and in there, you create io and
 timer watchers as required by the other software. Here is a real-world
 example of integrating Net::SNMP (with some details left out):
    our @snmp_watcher;
 The callbacks of the created watchers will not be called as the watchers
 are destroyed before this can happen (remember EV::check gets called
 first).
 The C<check_ns> variant doesn't start (activate) the newly created watcher.
+=item EV::CHECK constant issues
+Like all other watcher types, there is a bitmask constant for use in
+C<$revents> and other places. The C<EV::CHECK> is special as it has
+the same name as the C<CHECK> sub called by Perl. This doesn't cause
+big issues on newer perls (beginning with 5.8.9), but it means thatthe
+constant must be I<inlined>, i.e. runtime calls will not work. That means
+that as long as you always C<use EV> and then C<EV::CHECK> you are on the
+safe side.
 =back
 =head3 FORK WATCHERS - the audacity to resume the event loop after a fork
 =item $w = EV::async $callback
 =item $w = EV::async_ns $callback
+=item $w = $loop->async ($callback)
+=item $w = $loop->async_ns ($callback)
 =item $w->send
 =item $bool = $w->async_pending
 =back
+=head3 CLEANUP WATCHERS - how to clean up when the event loop goes away
+Cleanup watchers are not supported on the Perl level, they can only be
+used via XS currently.
 =head1 PERL SIGNALS
 While Perl signal handling (C<%SIG>) is not affected by EV, the behaviour
 1;
 =head1 SEE ALSO
+L<EV::MakeMaker> - MakeMaker interface to XS API, L<EV::ADNS>
-L<EV::ADNS> (asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as
+(asynchronous DNS), L<Glib::EV> (makes Glib/Gtk2 use EV as event
-event loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient
+loop), L<EV::Glib> (embed Glib into EV), L<Coro::EV> (efficient thread
-coroutines with EV), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for
+integration), L<Net::SNMP::EV> (asynchronous SNMP), L<AnyEvent> for
 event-loop agnostic and portable event driven programming.
 =head1 AUTHOR
    Marc Lehmann <schmorp@schmorp.de>

Diff Legend

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

Comparing EV/EV.pm (file contents): Revision 1.117 by root, Tue Jul 14 00:09:59 2009 UTC vs. Revision 1.151 by root, Tue Sep 4 23:14:45 2018 UTC

Diff Legend

Comparing EV/EV.pm (file contents):
Revision 1.117 by root, Tue Jul 14 00:09:59 2009 UTC vs.
Revision 1.151 by root, Tue Sep 4 23:14:45 2018 UTC