summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2008-10-21 20:52:30 +0000
committerroot <root>2008-10-21 20:52:30 +0000
commite18edf2b394650ac41062113ebb0750d493e18c3 (patch)
tree5016cbe7bc23d1ad71ae3ca118c037aba20d8468 /ev.pod
parent69f8044b5857f2492f6b7a3eb58ec1cc1b455bf1 (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod8
1 files changed, 6 insertions, 2 deletions
diff --git a/ev.pod b/ev.pod
index dc76872..958a8c2 100644
--- a/ev.pod
+++ b/ev.pod
@@ -896,8 +896,12 @@ The given async watcher has been asynchronously notified (see C<ev_async>).
An unspecified error has occurred, the watcher has been stopped. This might
happen because the watcher could not be properly started because libev
ran out of memory, a file descriptor was found to be closed or any other
-problem. You best act on it by reporting the problem and somehow coping
-with the watcher being stopped.
+problem. Libev considers these application bugs.
+
+You best act on it by reporting the problem and somehow coping with the
+watcher being stopped. Note that well-written programs should not receive
+an error ever, so when your watcher receives it, this usually indicates a
+bug in your program.
Libev will usually signal a few "dummy" events together with an error, for
example it might indicate that a fd is readable or writable, and if your