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

Comparing EV/EV.pm (file contents):
Revision 1.154 by root, Fri Dec 21 07:06:51 2018 UTC vs.
Revision 1.167 by root, Thu Oct 19 18:02:42 2023 UTC

 package EV;
 use common::sense;
 BEGIN {
-   our $VERSION = 4.25;
+   our $VERSION = '4.34';
    use XSLoader;
    local $^W = 0; # avoid spurious warning
    XSLoader::load "EV", $VERSION;
 }
 or locally-installed as F<EV::libev> manpage) for more info.
 The loop will automatically be destroyed when it is no longer referenced
 by any watcher and the loop object goes out of scope.
-If you are not embedding the loop, then Using C<EV::FLAG_FORKCHECK>
+If you are not embedding the loop, then using C<EV::FLAG_FORKCHECK>
 is recommended, as only the default event loop is protected by this
 module. If you I<are> embedding this loop in the default loop, this is not
 necessary, as C<EV::embed> automatically does the right thing on fork.
 =item $loop->loop_fork
 =item $loop->now_update
 Establishes the current time by querying the kernel, updating the time
 returned by C<EV::now> in the progress. This is a costly operation and
-is usually done automatically within C<EV::loop>.
+is usually done automatically within C<EV::run>.
 This function is rarely useful, but when some event callback runs for a
 very long time without entering the event loop, updating libev's idea of
 the current time is a good idea.
 =item EV::break [$how]
 =item $loop->break ([$how])
 When called with no arguments or an argument of EV::BREAK_ONE, makes the
-innermost call to EV::loop return.
+innermost call to EV::run return.
-When called with an argument of EV::BREAK_ALL, all calls to EV::loop will
+When called with an argument of EV::BREAK_ALL, all calls to EV::run will
 return as fast as possible.
 When called with an argument of EV::BREAK_CANCEL, any pending break will
 be cancelled.
 =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.
+for custom signal implementations.
 =item EV::set_io_collect_interval $time
 =item $loop->set_io_collect_interval ($time)
 returns its C<$revents> bitset (as if its callback was invoked). If the
 watcher isn't pending it does nothing and returns C<0>.
 =item $previous_state = $w->keepalive ($bool)
-Normally, C<EV::loop> will return when there are no active watchers
+Normally, C<EV::run> will return when there are no active watchers
 (which is a "deadlock" because no progress can be made anymore). This is
 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
+call C<EV::run> 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
+that calls C<EV::run> (usually the main program) is not the same module
 as a long-living watcher (for example a DNS client module written by
 somebody else even). Then you might want any outstanding requests to be
-handled, but you would not want to keep C<EV::loop> from returning just
+handled, but you would not want to keep C<EV::run> from returning just
 because you happen to have this long-running UDP port watcher.
 In this case you can clear the keepalive status, which means that even
-though your watcher is active, it won't keep C<EV::loop> from returning.
+though your watcher is active, it won't keep C<EV::run> from returning.
 The initial value for keepalive is true (enabled), and you can change it
 any time.
 Example: Register an I/O watcher for some UDP socket but do not keep the
 value.
 =item $after = $w->remaining
 Calculates and returns the remaining time till the timer will fire.
+=item $repeat = $w->repeat
+=item $old_repeat = $w->repeat ($new_repeat)
+Returns the current value of the repeat attribute and optionally sets a
+new one. Setting the new one will not restart the watcher - if the watcher
+is active, the new repeat value is used whenever it expires next.
 =back
 =head3 PERIODIC WATCHERS - to cron or not to cron?
 =item $time = $w->at
 Return the time that the watcher is expected to trigger next.
+=item $offset = $w->offset
+=item $old_offset = $w->offset ($new_offset)
+Returns the current value of the offset attribute and optionally sets a
+new one. Setting the new one will not restart the watcher - if the watcher
+is active, the new offset value is used whenever it expires next.
+=item $interval = $w->interval
+=item $old_interval = $w->interval ($new_interval)
+See above, for the interval attribute.
+=item $reschedule_cb = $w->reschedule_cb
+=item $old_reschedule_cb = $w->reschedule_cb ($new_reschedule_cb)
+See above, for the reschedule callback.
 =back
 =head3 SIGNAL WATCHERS - signal me when a signal gets signalled!
 =item $pid = $w->rpid
 Return the pid of the awaited child (useful when you have installed a
 watcher for all pids).
+=item EV::Child::reinit [EXPERIMENTAL]
+Internally, libev installs a signal handler for C<SIGCHLD>. Unfortunately,
+a lot of Perl code does soemthing like C<< local $SIG{CHLD} >>, which,
+unfortunately, is broken and will not restore the signal handler.
+If this has happened, you can call this function to stop/rrestart the
+internal libev watcher, which will reset the signal handler.
+Note that this is an experimental function, whose interface might change.
 =back
 =head3 STAT WATCHERS - did the file attributes just change?

Diff Legend

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

Comparing EV/EV.pm (file contents): Revision 1.154 by root, Fri Dec 21 07:06:51 2018 UTC vs. Revision 1.167 by root, Thu Oct 19 18:02:42 2023 UTC

Diff Legend

Comparing EV/EV.pm (file contents):
Revision 1.154 by root, Fri Dec 21 07:06:51 2018 UTC vs.
Revision 1.167 by root, Thu Oct 19 18:02:42 2023 UTC