From 56dce0a1998a41311a02bda53fb827041e14b699 Mon Sep 17 00:00:00 2001 From: root Date: Sun, 6 Jul 2008 03:36:51 +0000 Subject: 3.43 --- Changes | 4 ++-- ev.3 | 7 ++++--- 2 files changed, 6 insertions(+), 5 deletions(-) diff --git a/Changes b/Changes index 345915e..44f4bcf 100644 --- a/Changes +++ b/Changes @@ -1,8 +1,8 @@ Revision history for libev, a high-performance and full-featured event loop. -3.43 +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 in ev.c on windows (reported by Matt Tolton). 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. -- cgit v1.2.3