X-Git-Url: https://git.llucax.com/software/libev.git/blobdiff_plain/8e61f07d52c0b46222c8be6f32914ada9fbe714b..6a1fe0fbe0b1094997e8e6d22c1de8fda64f3a40:/ev.html?ds=sidebyside diff --git a/ev.html b/ev.html index 4837317..6a77ae7 100644 --- a/ev.html +++ b/ev.html @@ -6,7 +6,7 @@ - +
@@ -19,7 +19,8 @@loop
(which is always of type struct ev_loop
will not have this argument.
-TIME AND OTHER GLOBAL FUNCTIONS
-
+TIME REPRESENTATION
+
Libev represents time as a single floating point number, representing the
(fractional) number of seconds since the (POSIX) epoch (somewhere near
the beginning of 1970, details are complicated, don't ask). This type is
called ev_tstamp
, which is what you should use too. It usually aliases
to the double type in C.
+
+
+GLOBAL FUNCTIONS
+
- ev_tstamp ev_time ()
-
@@ -144,7 +149,7 @@ requested operation, or, if the condition doesn't go away, do bad stuff
types of such loops, the default loop, which supports signals and child
events, and dynamically created loops which do not.
If you use threads, a common model is to run the default event loop
-in your main thread (or in a separate thrad) and for each thread you
+in your main thread (or in a separate thread) and for each thread you
create, you also create another event loop. Libev itself does no locking
whatsoever, so if you mix calls to the same event loop in different
threads, make sure you lock (this is usually a bad idea, though, even if
@@ -664,8 +669,8 @@ believe me.
-prepare and check - your hooks into the event loop
-
+ev_prepare
and ev_check
- customise your event loop
+
Prepare and check watchers are usually (but not always) used in tandem:
Prepare watchers get invoked before the process blocks and check watchers
afterwards.