summaryrefslogtreecommitdiff
path: root/ev.pod
diff options
context:
space:
mode:
authorroot <root>2007-11-23 04:36:03 +0000
committerroot <root>2007-11-23 04:36:03 +0000
commit1ad1e600c3eebe009db39a0f9750ed4adb078857 (patch)
tree1434a2197a77b34a95b18b641e7e72081f4c17fe /ev.pod
parent464fbfae8cba64110c7764620d80fb91cd988618 (diff)
*** empty log message ***
Diffstat (limited to 'ev.pod')
-rw-r--r--ev.pod6
1 files changed, 3 insertions, 3 deletions
diff --git a/ev.pod b/ev.pod
index 9845aff..30c164a 100644
--- a/ev.pod
+++ b/ev.pod
@@ -236,9 +236,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).
-You I<must> 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 I<must> 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.
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