summaryrefslogtreecommitdiff
path: root/ev.3
diff options
context:
space:
mode:
authorroot <root>2008-07-06 03:36:51 +0000
committerroot <root>2008-07-06 03:36:51 +0000
commit56dce0a1998a41311a02bda53fb827041e14b699 (patch)
treea78b321a579db982ff06d9eb2f21b67af7397320 /ev.3
parentefe43f1ea2f1d6a2238c7bba16d31d2e773abae9 (diff)
Diffstat (limited to 'ev.3')
-rw-r--r--ev.37
1 files changed, 4 insertions, 3 deletions
diff --git a/ev.3 b/ev.3
index 6852bd3..39b9f24 100644
--- a/ev.3
+++ b/ev.3
@@ -132,7 +132,7 @@
.\" ========================================================================
.\"
.IX Title "LIBEV 3"
-.TH LIBEV 3 "2008-06-19" "libev-3.43" "libev - high performance full featured event loop"
+.TH LIBEV 3 "2008-07-05" "libev-3.43" "libev - high performance full featured event loop"
.\" For nroff, turn off justification. Always turn off hyphenation; it makes
.\" way too many mistakes in technical documents.
.if n .ad l
@@ -3275,8 +3275,9 @@ done serially (but can be done from different threads, as long as only one
thread ever is inside a call at any point in time, e.g. by using a mutex
per loop).
.PP
-If you want to know which design is best for your problem, then I cannot
-help you but by giving some generic advice:
+If you want to know which design (one loop, locking, or multiple loops
+without or something else still) is best for your problem, then I cannot
+help you. I can give some generic advice however:
.IP "\(bu" 4
most applications have a main thread: use the default libev loop
in that thread, or create a separate thread running only the default loop.