renamed METHODs to BACKENDs

[software/libev.git] / ev.3

diff --git a/ev.3 b/ev.3
index 190f657f271e7669d5b7fabec45b828a660249fc..5fda0313c33f5dd523af71d11266490a404002f3 100644 (file)
--- a/ev.3
+++ b/ev.3
@@ -129,7 +129,7 @@
 .\" ========================================================================
 .\"
 .IX Title ""<STANDARD INPUT>" 1"
-.TH "<STANDARD INPUT>" 1 "2007-11-22" "perl v5.8.8" "User Contributed Perl Documentation"
+.TH "<STANDARD INPUT>" 1 "2007-11-23" "perl v5.8.8" "User Contributed Perl Documentation"
 .SH "NAME"
 libev \- a high performance full\-featured event loop written in C
 .SH "SYNOPSIS"
@@ -316,8 +316,9 @@ it's really slow, but it still scales very well (O(active_fds)).
 .ie n .IP """EVMETHOD_ALL""" 4
 .el .IP "\f(CWEVMETHOD_ALL\fR" 4
 .IX Item "EVMETHOD_ALL"
-Try all backends (even potentially broken ones). Since this is a mask, you
-can do stuff like \f(CW\*(C`EVMETHOD_ALL & ~EVMETHOD_KQUEUE\*(C'\fR.
+Try all backends (even potentially broken ones that wouldn't be tried
+with \f(CW\*(C`EVFLAG_AUTO\*(C'\fR). Since this is a mask, you can do stuff such as
+\&\f(CW\*(C`EVMETHOD_ALL & ~EVMETHOD_KQUEUE\*(C'\fR.
 .RE
 .RS 4
 .Sp
@@ -348,9 +349,9 @@ one. Despite the name, you can call it anytime, but it makes most sense
 after forking, in either the parent or child process (or both, but that
 again makes little sense).
 .Sp
-You \fImust\fR call this function after forking if and only if you want to
-use the event library in both processes. If you just fork+exec, you don't
-have to call it.
+You \fImust\fR call this function in the child process after forking if and
+only if you want to use the event library in both processes. If you just
+fork+exec, you don't have to call it.
 .Sp
 The function itself is quite fast and it's usually not a problem to call
 it just in case after a fork. To make this easy, the function will fit in