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

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.49 by root, Mon Apr 14 19:11:15 2008 UTC vs.
Revision 1.52 by root, Sat Apr 19 03:47:24 2008 UTC

 =head1 NAME
 AnyEvent - provide framework for multiple event loops
-Event, Coro, Glib, Tk, Perl - various supported event loops
+EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl - various supported event loops
 =head1 SYNOPSIS
    use AnyEvent;
    my $w = AnyEvent->timer (after => $seconds, cb => sub {
       ...
    });
-   my $w = AnyEvent->condvar; # stores wether a condition was flagged
+   my $w = AnyEvent->condvar; # stores whether a condition was flagged
    $w->wait; # enters "main loop" till $condvar gets ->broadcast
    $w->broadcast; # wake up current and all future wait's
 =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT)
 The interface itself is vaguely similar but not identical to the Event
 module.
 On the first call of any method, the module tries to detect the currently
-loaded event loop by probing wether any of the following modules is
+loaded event loop by probing whether any of the following modules is
-loaded: L<Coro::Event>, L<Event>, L<Glib>, L<Tk>. The first one found is
+loaded: L<Coro::EV>, L<Coro::Event>, L<EV>, L<Event>, L<Glib>, L<Tk>. The
-used. If none is found, the module tries to load these modules in the
+first one found is used. If none are found, the module tries to load these
-order given. The first one that could be successfully loaded will be
+modules in the order given. The first one that could be successfully
-used. If still none could be found, AnyEvent will fall back to a pure-perl
+loaded will be used. If still none could be found, AnyEvent will fall back
-event loop, which is also not very efficient.
+to a pure-perl event loop, which is also not very efficient.
 Because AnyEvent first checks for modules that are already loaded, loading
 an Event model explicitly before first using AnyEvent will likely make
 that model the default. For example:
 C<fh> the Perl I<filehandle> (not filedescriptor) to watch for
 events. C<poll> must be a string that is either C<r> or C<w>, that creates
 a watcher waiting for "r"eadable or "w"ritable events. C<cb> the callback
 to invoke everytime the filehandle becomes ready.
-Only one io watcher per C<fh> and C<poll> combination is allowed (i.e. on
-a socket you can have one r + one w, not any more (limitation comes from
-Tk - if you are sure you are not using Tk this limitation is gone).
 Filehandles will be kept alive, so as long as the watcher exists, the
 filehandle exists, too.
 Example:
 immediately.
 Not all event models support a blocking wait - some die in that case
 (programs might want to do that so they stay interactive), so I<if you
 are using this from a module, never require a blocking wait>, but let the
-caller decide wether the call will block or not (for example, by coupling
+caller decide whether the call will block or not (for example, by coupling
 condition variables with some kind of request results and supporting
 callbacks so the caller knows that getting the result will not block,
 while still suppporting blocking waits if the caller so desires).
 Another reason I<never> to C<< ->wait >> in a module is that you cannot
 AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>).
 The known classes so far are:
    AnyEvent::Impl::CoroEV    based on Coro::EV, best choice.
+   AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
    AnyEvent::Impl::EV        based on EV (an interface to libev, also best choice).
-   AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice.
    AnyEvent::Impl::Event     based on Event, also second best choice :)
    AnyEvent::Impl::Glib      based on Glib, third-best choice.
    AnyEvent::Impl::Tk        based on Tk, very bad choice.
    AnyEvent::Impl::Perl      pure-perl implementation, inefficient but portable.
 no warnings;
 use strict;
 use Carp;
-our $VERSION = '3.0';
+our $VERSION = '3.1';
 our $MODEL;
 our $AUTOLOAD;
 our @ISA;
 our @REGISTRY;
 my @models = (
    [Coro::EV::             => AnyEvent::Impl::CoroEV::],
+   [Coro::Event::          => AnyEvent::Impl::CoroEvent::],
    [EV::                   => AnyEvent::Impl::EV::],
-   [Coro::Event::          => AnyEvent::Impl::CoroEvent::],
    [Event::                => AnyEvent::Impl::Event::],
    [Glib::                 => AnyEvent::Impl::Glib::],
    [Tk::                   => AnyEvent::Impl::Tk::],
    [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::],
 );
    $txn->{finished}->wait;
    return $txn->{result};
 The actual code goes further and collects all errors (C<die>s, exceptions)
 that occured during request processing. The C<result> method detects
-wether an exception as thrown (it is stored inside the $txn object)
+whether an exception as thrown (it is stored inside the $txn object)
 and just throws the exception, which means connection errors and other
 problems get reported tot he code that tries to use the result, not in a
 random callback.
 All of this enables the following usage styles:

Diff Legend

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

Comparing AnyEvent/lib/AnyEvent.pm (file contents): Revision 1.49 by root, Mon Apr 14 19:11:15 2008 UTC vs. Revision 1.52 by root, Sat Apr 19 03:47:24 2008 UTC

Diff Legend

Comparing AnyEvent/lib/AnyEvent.pm (file contents):
Revision 1.49 by root, Mon Apr 14 19:11:15 2008 UTC vs.
Revision 1.52 by root, Sat Apr 19 03:47:24 2008 UTC