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

Comparing libev/ev.pod (file contents):
Revision 1.393 by root, Sat Jan 21 12:23:45 2012 UTC vs.
Revision 1.397 by root, Mon Feb 13 01:52:14 2012 UTC

 keep up with the timer (because it takes longer than those 10 seconds to
 do stuff) the timer will not fire more than once per event loop iteration.
 =item ev_timer_again (loop, ev_timer *)
-This will act as if the timer timed out and restarts it again if it is
+This will act as if the timer timed out, and restarts it again if it is
-repeating. The exact semantics are:
+repeating. It basically works like calling C<ev_timer_stop>, updating the
+timeout to the C<repeat> value and calling C<ev_timer_start>.
+The exact semantics are as in the following rules, all of which will be
+applied to the watcher:
+=over 4
-If the timer is pending, its pending status is cleared.
+=item If the timer is pending, the pending status is always cleared.
-If the timer is started but non-repeating, stop it (as if it timed out).
+=item If the timer is started but non-repeating, stop it (as if it timed
+out, without invoking it).
-If the timer is repeating, either start it if necessary (with the
+=item If the timer is repeating, make the C<repeat> value the new timeout
-C<repeat> value), or reset the running timer to the C<repeat> value.
+and start the timer, if necessary.
+=back
 This sounds a bit complicated, see L<Be smart about timeouts>, above, for a
 usage example.
 =item ev_tstamp ev_timer_remaining (loop, ev_timer *)
 with C<operator ()> can be used as callbacks. Other types should be easy
 to add as long as they only need one additional pointer for context. If
 you need support for other types of functors please contact the author
 (preferably after implementing it).
+For all this to work, your C++ compiler either has to use the same calling
+conventions as your C compiler (for static member functions), or you have
+to embed libev and compile libev itself as C++.
 Here is a list of things available in the C<ev> namespace:
 =over 4
 =item C<ev::READ>, C<ev::WRITE> etc.
 If defined to be C<1>, libev will compile in support for the Linux inotify
 interface to speed up C<ev_stat> watchers. Its actual availability will
 be detected at runtime. If undefined, it will be enabled if the headers
 indicate GNU/Linux + Glibc 2.4 or newer, otherwise disabled.
+=item EV_NO_SMP
+If defined to be C<1>, libev will assume that memory is always coherent
+between threads, that is, threads can be used, but threads never run on
+different cpus (or different cpu cores). This reduces dependencies
+and makes libev faster.
+=item EV_NO_THREADS
+If defined to be C<1>, libev will assume that it will never be called
+from different threads, which is a stronger assumption than C<EV_NO_SMP>,
+above. This reduces dependencies and makes libev faster.
 =item EV_ATOMIC_T
 Libev requires an integer type (suitable for storing C<0> or C<1>) whose
 access is atomic and serialised with respect to other threads or signal
 contexts. No such type is easily found in the C language, so you can

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.393 by root, Sat Jan 21 12:23:45 2012 UTC vs. Revision 1.397 by root, Mon Feb 13 01:52:14 2012 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.393 by root, Sat Jan 21 12:23:45 2012 UTC vs.
Revision 1.397 by root, Mon Feb 13 01:52:14 2012 UTC