GLOBAL FUNCTIONS

@@ -607,6 +605,15 @@ received events. Callbacks of both watcher types can start and stop as many watchers as they want, and all of them will be taken into account (for example, a ev_prepare watcher might start an idle watcher to keep ev_loop from blocking).

+ +

EV_EMBED

The embedded event loop specified in the ev_embed watcher needs attention.

EV_FORK

The event loop has been resumed in the child process after fork (see +ev_fork).

EV_ERROR

@@ -1481,6 +1488,29 @@ apropriate way for embedded loops.

ev_fork - the audacity to resume the event loop after a fork

Fork watchers are called when a fork () was detected (usually because +whoever is a good citizen cared to tell libev about it by calling +ev_default_fork or ev_loop_fork). The invocation is done before the +event loop blocks next and before ev_check watchers are being called, +and only in the child after the fork. If whoever good citizen calling +ev_default_fork cheats and calls it in the wrong process, the fork +handlers will be invoked, too, of course.

ev_fork_init (ev_signal *, callback): +
Initialises and configures the fork watcher - it has no parameters of any +kind. There is a ev_fork_set macro, but using it is utterly pointless, +believe me.
+

+ + + + +

OTHER FUNCTIONS

MACRO MAGIC

Libev can be compiled with a variety of options, the most fundemantal is +EV_MULTIPLICITY. This option determines wether (most) functions and +callbacks have an initial struct ev_loop * argument.

To make it easier to write programs that cope with either variant, the +following macros are defined:

EV_A, EV_A_

This provides the loop argument for functions, if one is required ("ev +loop argument"). The EV_A form is used when this is the sole argument, +EV_A_ is used when other arguments are following. Example:

  ev_unref (EV_A);
+  ev_timer_add (EV_A_ watcher);
+  ev_loop (EV_A_ 0);
+
+

It assumes the variable loop of type struct ev_loop * is in scope, +which is often provided by the following macro.

EV_P, EV_P_

This provides the loop parameter for functions, if one is required ("ev +loop parameter"). The EV_P form is used when this is the sole parameter, +EV_P_ is used when other parameters are following. Example:

  // this is how ev_unref is being declared
+  static void ev_unref (EV_P);
+
+  // this is how you can declare your typical callback
+  static void cb (EV_P_ ev_timer *w, int revents)
+
+

It declares a parameter loop of type struct ev_loop *, quite +suitable for use with EV_A.

EV_DEFAULT, EV_DEFAULT_

Similar to the other two macros, this gives you the value of the default +loop, if multiple loops are supported ("ev loop default").

Example: Declare and initialise a check watcher, working regardless of +wether multiple loops are supported or not.

  static void
+  check_cb (EV_P_ ev_timer *w, int revents)
+  {
+    ev_check_stop (EV_A_ w);
+  }
+
+  ev_check check;
+  ev_check_init (&check, check_cb);
+  ev_check_start (EV_DEFAULT_ &check);
+  ev_loop (EV_DEFAULT_ 0);
+
+
+
+

GLOBAL FUNCTIONS

ev_fork - the audacity to resume the event loop after a fork

OTHER FUNCTIONS

MACRO MAGIC

`ev_fork` - the audacity to resume the event loop after a fork