--- AnyEvent/lib/AnyEvent.pm	2008/04/25 13:32:39	1.82
+++ AnyEvent/lib/AnyEvent.pm	2008/04/25 13:48:42	1.84
@@ -150,13 +150,17 @@
 becomes ready.
 
 The I/O watcher might use the underlying file descriptor or a copy of it.
-It is not allowed to close a file handle as long as any watcher is active
-on the underlying file descriptor.
+You must not close a file handle as long as any watcher is active on the
+underlying file descriptor.
 
 Some event loops issue spurious readyness notifications, so you should
 always use non-blocking calls when reading/writing from/to your file
 handles.
 
+Although the callback might get passed parameters, their value and
+presence is undefined and you cannot rely on them. Portable AnyEvent
+callbacks cannot use arguments passed to I/O watcher callbacks.
+
 Example:
 
    # wait for readability of STDIN, then read a line and disable the watcher
@@ -179,6 +183,10 @@
 timer you have to create a new watcher (this is a limitation by both Tk
 and Glib).
 
+Although the callback might get passed parameters, their value and
+presence is undefined and you cannot rely on them. Portable AnyEvent
+callbacks cannot use arguments passed to time watcher callbacks.
+
 Example:
 
    # fire an event after 7.7 seconds
@@ -928,15 +936,15 @@
 
           name watchers bytes create invoke destroy comment
          EV/EV   400000   244   0.56   0.46    0.31 EV native interface
-        EV/Any   100000   610   3.52   0.91    0.75 EV + AnyEvent watchers
-    CoroEV/Any   100000   610   3.49   0.92    0.75 coroutines + Coro::Signal
-      Perl/Any   100000   513   4.91   0.92    1.15 pure perl implementation
-   Event/Event    16000   523  28.05  21.38    0.86 Event native interface
-     Event/Any    16000   943  34.43  20.48    1.39 Event + AnyEvent watchers
-      Glib/Any    16000  1357  96.99  12.55   55.51 quadratic behaviour
-        Tk/Any     2000  1855  27.01  66.61   14.03 SEGV with >> 2000 watchers
-     POE/Event     2000  6644 108.15 768.19   14.33 via POE::Loop::Event
-    POE/Select     2000  6343  94.69 807.65  562.69 via POE::Loop::Select
+        EV/Any   100000   244   2.50   0.46    0.29 EV + AnyEvent watchers
+    CoroEV/Any   100000   244   2.49   0.44    0.29 coroutines + Coro::Signal
+      Perl/Any   100000   513   4.92   0.87    1.12 pure perl implementation
+   Event/Event    16000   516  31.88  31.30    0.85 Event native interface
+     Event/Any    16000   936  39.17  33.63    1.43 Event + AnyEvent watchers
+      Glib/Any    16000  1357  98.22  12.41   54.00 quadratic behaviour
+        Tk/Any     2000  1860  26.97  67.98   14.00 SEGV with >> 2000 watchers
+     POE/Event     2000  6644 108.64 736.02   14.73 via POE::Loop::Event
+    POE/Select     2000  6343  94.13 809.12  565.96 via POE::Loop::Select
 
 =head2 Discussion
 
@@ -948,10 +956,9 @@
 boost.
 
 C<EV> is the sole leader regarding speed and memory use, which are both
-maximal/minimal, respectively. Even when going through AnyEvent, there are
-only two event loops that use slightly less memory (the C<Event> module
-natively and the pure perl backend), and no faster event models, not even
-C<Event> natively.
+maximal/minimal, respectively. Even when going through AnyEvent, it uses
+far less memory than any other event loop and is still faster than Event
+natively.
 
 The pure perl implementation is hit in a few sweet spots (both the
 zero timeout and the use of a single fd hit optimisations in the perl