[ViewVC] Diff of: cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.124 by root, Fri Feb 1 13:41:03 2008 UTC vs.
Revision 1.127 by root, Fri Feb 1 13:47:08 2008 UTC

    {
      sometype data;
      // no locking etc.
      queue_put (data);
-     ev_async_send (DEFAULT_LOOP, &mysig);
+     ev_async_send (DEFAULT_ &mysig);
    }
    static void
    mysig_cb (EV_P_ ev_async *w, int revents)
    {
      // only need to lock the actual queueing operation
      pthread_mutex_lock (&mymutex);
      queue_put (data);
      pthread_mutex_unlock (&mymutex);
-     ev_async_send (DEFAULT_LOOP, &mysig);
+     ev_async_send (DEFAULT_ &mysig);
    }
    static void
    mysig_cb (EV_P_ ev_async *w, int revents)
    {
 be detected at runtime.
 =item EV_ATOMIC_T
 Libev requires an integer type (suitable for storing C<0> or C<1>) whose
-access is atomic with respect to other threads or signal contexts. No such type
+access is atomic with respect to other threads or signal contexts. No such
-is easily found using, so you cna provide your own type that you know is safe.
+type is easily found in the C language, so you can provide your own type
+that you know is safe for your purposes. It is used both for signal handler "locking"
+as well as for signal and thread safety in C<ev_async> watchers.
 In the absense of this define, libev will use C<sig_atomic_t volatile>
-from F<signal.h>, which is usually good enough on most platforms.
+(from F<signal.h>), which is usually good enough on most platforms.
 =item EV_H
 The name of the F<ev.h> header file used to include it. The default if
 undefined is C<"ev.h"> in F<event.h>, F<ev.c> and F<ev++.h>. This can be

-–
+Removed lines
-+
+Added lines
-<
+Changed lines
->
+Changed lines