@ -1,8 +1,8 @@
Revision history for libev, a high-performance and full-featured event loop.
3.43 Sun Jul 6 05:34:41 CEST 2008
- include more include files on windows to get struct _stati64
(reported by Chris Hulbert).
(reported by Chris Hulbert, but doesn't quite fix his issue).
- add missing #include <io.h> in ev.c on windows (reported by
@ -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
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.