--- AnyEvent/lib/AnyEvent.pm 2008/04/16 15:10:10 1.51 +++ AnyEvent/lib/AnyEvent.pm 2008/04/19 03:47:24 1.52 @@ -16,7 +16,7 @@ ... }); - 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 @@ -76,7 +76,7 @@ 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, L, L, L, L, L. The first one found is used. If none are found, the module tries to load these modules in the order given. The first one that could be successfully @@ -183,7 +183,7 @@ 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, 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). @@ -629,7 +629,7 @@ The actual code goes further and collects all errors (Cs, exceptions) that occured during request processing. The C 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.