[ViewVC] Diff of: cvs/AnyEvent/lib/AnyEvent.pm

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.279 by root, Sun Aug 9 16:05:11 2009 UTC vs.
Revision 1.297 by root, Thu Nov 19 01:55:57 2009 UTC

 this "current" time will differ substantially from the real time, which
 might affect timers and time-outs.
 When this is the case, you can call this method, which will update the
 event loop's idea of "current time".
+A typical example would be a script in a web server (e.g. C<mod_perl>) -
+when mod_perl executes the script, then the event loop will have the wrong
+idea about the "current time" (being potentially far in the past, when the
+script ran the last time). In that case you should arrange a call to C<<
+AnyEvent->now_update >> each time the web server process wakes up again
+(e.g. at the start of your script, or in a handler).
 Note that updating the time I<might> cause some events to be handled.
 =back
       after => 1,
       cb    => sub { $result_ready->send },
    );
    # this "blocks" (while handling events) till the callback
-   # calls -<send
+   # calls ->send
    $result_ready->recv;
 Example: wait for a timer, but take advantage of the fact that condition
 variables are also callable directly.
 one. For example, a function that pings many hosts in parallel might want
 to use a condition variable for the whole process.
 Every call to C<< ->begin >> will increment a counter, and every call to
 C<< ->end >> will decrement it.  If the counter reaches C<0> in C<< ->end
->>, the (last) callback passed to C<begin> will be executed. That callback
+>>, the (last) callback passed to C<begin> will be executed, passing the
-is I<supposed> to call C<< ->send >>, but that is not required. If no
+condvar as first argument. That callback is I<supposed> to call C<< ->send
-callback was set, C<send> will be called without any arguments.
+>>, but that is not required. If no group callback was set, C<send> will
+be called without any arguments.
 You can think of C<< $cv->send >> giving you an OR condition (one call
 sends), while C<< $cv->begin >> and C<< $cv->end >> giving you an AND
 condition (all C<begin> calls must be C<end>'ed before the condvar sends).
 begung can potentially be zero:
    my $cv = AnyEvent->condvar;
    my %result;
-   $cv->begin (sub { $cv->send (\%result) });
+   $cv->begin (sub { shift->send (\%result) });
    for my $host (@list_of_hosts) {
       $cv->begin;
       ping_host_then_call_callback $host, sub {
          $result{$host} = ...;
 package AnyEvent;
 # basically a tuned-down version of common::sense
 sub common_sense {
-   # no warnings
+   # from common:.sense 1.0
-   ${^WARNING_BITS} ^= ${^WARNING_BITS};
+   ${^WARNING_BITS} = "\xfc\x3f\xf3\x00\x0f\xf3\xcf\xc0\xf3\xfc\x33\x03";
    # use strict vars subs
    $^H |= 0x00000600;
 }
 BEGIN { AnyEvent::common_sense }
 use Carp ();
-our $VERSION = '5.0';
+our $VERSION = '5.21';
 our $MODEL;
 our $AUTOLOAD;
 our @ISA;
 our @REGISTRY;
-our $WIN32;
 our $VERBOSE;
 BEGIN {
    eval "sub WIN32(){ " . (($^O =~ /mswin32/i)*1) ." }";
 package AnyEvent::Base;
 # default implementations for many methods
-sub _time {
+sub _time() {
    # probe for availability of Time::HiRes
    if (eval "use Time::HiRes (); Time::HiRes::time (); 1") {
       warn "AnyEvent: using Time::HiRes for sub-second timing accuracy.\n" if $VERBOSE >= 8;
       *_time = \&Time::HiRes::time;
       # if (eval "use POSIX (); (POSIX::times())...
 our $HAVE_ASYNC_INTERRUPT;
 sub _have_async_interrupt() {
    $HAVE_ASYNC_INTERRUPT = 1*(!$ENV{PERL_ANYEVENT_AVOID_ASYNC_INTERRUPT}
-                              && eval "use Async::Interrupt 1.0 (); 1")
+                              && eval "use Async::Interrupt 1.02 (); 1")
       unless defined $HAVE_ASYNC_INTERRUPT;
    $HAVE_ASYNC_INTERRUPT
 }
 our ($SIG_COUNT, $SIG_TW);
 sub _signal_exec {
    $HAVE_ASYNC_INTERRUPT
       ? $SIGPIPE_R->drain
-      : sysread $SIGPIPE_R, my $dummy, 9;
+      : sysread $SIGPIPE_R, (my $dummy), 9;
    while (%SIG_EV) {
       for (keys %SIG_EV) {
          delete $SIG_EV{$_};
          $_->() for values %{ $SIG_CB{$_} || {} };
          warn "read: $input\n";       # output what has been read
          $cv->send if $input =~ /^q/i; # quit program if /^q/i
       },
    );
-   my $time_watcher; # can only be used once
-   sub new_timer {
-      $timer = AnyEvent->timer (after => 1, cb => sub {
+   my $time_watcher = AnyEvent->timer (after => 1, interval => 1, cb => sub {
-         warn "timeout\n"; # print 'timeout' about every second
+      warn "timeout\n"; # print 'timeout' at most every second
-         &new_timer; # and restart the time
-      });
+   });
-   }
-   new_timer; # create first timer
    $cv->recv; # wait until user enters /^q/i
 =head1 REAL-WORLD EXAMPLE
 As you can see, the AnyEvent + EV combination even beats the
 hand-optimised "raw sockets benchmark", while AnyEvent + its pure perl
 backend easily beats IO::Lambda and POE.
 And even the 100% non-blocking version written using the high-level (and
-slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda by a
+slow :) L<AnyEvent::Handle> abstraction beats both POE and IO::Lambda
-large margin, even though it does all of DNS, tcp-connect and socket I/O
+higher level ("unoptimised") abstractions by a large margin, even though
-in a non-blocking way.
+it does all of DNS, tcp-connect and socket I/O in a non-blocking way.
 The two AnyEvent benchmarks programs can be found as F<eg/ae0.pl> and
 F<eg/ae2.pl> in the AnyEvent distribution, the remaining benchmarks are
-part of the IO::lambda distribution and were used without any changes.
+part of the IO::Lambda distribution and were used without any changes.
 =head1 SIGNALS
 AnyEvent currently installs handlers for these signals:
 lot less memory), but otherwise doesn't affect guard operation much. It is
 purely used for performance.
 =item L<JSON> and L<JSON::XS>
-This module is required when you want to read or write JSON data via
+One of these modules is required when you want to read or write JSON data
-L<AnyEvent::Handle>. It is also written in pure-perl, but can take
+via L<AnyEvent::Handle>. It is also written in pure-perl, but can take
 advantage of the ultra-high-speed L<JSON::XS> module when it is installed.
 In fact, L<AnyEvent::Handle> will use L<JSON::XS> by default if it is
 installed.

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.279 by root, Sun Aug 9 16:05:11 2009 UTC vs. Revision 1.297 by root, Thu Nov 19 01:55:57 2009 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.279 by root, Sun Aug 9 16:05:11 2009 UTC vs.
Revision 1.297 by root, Thu Nov 19 01:55:57 2009 UTC