X-Git-Url: https://git.llucax.com/software/libev.git/blobdiff_plain/303b36d19decccc02135b0771a0fb0c07277fb17..6a1fe0fbe0b1094997e8e6d22c1de8fda64f3a40:/ev.html diff --git a/ev.html b/ev.html index 4a921e9..6a77ae7 100644 --- a/ev.html +++ b/ev.html @@ -6,7 +6,7 @@ - + @@ -19,7 +19,8 @@
  • DESCRIPTION
  • FEATURES
  • CONVENTIONS
    • -
  • TIME AND OTHER GLOBAL FUNCTIONS
    • +
  • TIME REPRESENTATION
    • +
  • GLOBAL FUNCTIONS
  • FUNCTIONS CONTROLLING THE EVENT LOOP
  • ANATOMY OF A WATCHER
  • OTHER FUNCTIONS
    • @@ -89,13 +90,17 @@ argument of name loop (which is always of type struct ev_loop will not have this argument.

    -

    TIME AND OTHER GLOBAL FUNCTIONS

    Top

    -
    +

    TIME REPRESENTATION

    Top

    +

    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

    Top

    +
    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.