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

Comparing libev/ev.pod (file contents):
Revision 1.58 by root, Wed Nov 28 11:31:34 2007 UTC vs.
Revision 1.66 by root, Mon Dec 3 13:41:25 2007 UTC

 C<ev_embeddable_backends () & ev_supported_backends ()>, likewise for
 recommended ones.
 See the description of C<ev_embed> watchers for more info.
-=item ev_set_allocator (void *(*cb)(void *ptr, size_t size))
+=item ev_set_allocator (void *(*cb)(void *ptr, long size))
-Sets the allocation function to use (the prototype and semantics are
+Sets the allocation function to use (the prototype is similar - the
-identical to the realloc C function). It is used to allocate and free
+semantics is identical - to the realloc C function). It is used to
-memory (no surprises here). If it returns zero when memory needs to be
+allocate and free memory (no surprises here). If it returns zero when
-allocated, the library might abort or take some potentially destructive
+memory needs to be allocated, the library might abort or take some
-action. The default is your system realloc function.
+potentially destructive action. The default is your system realloc
+function.
 You could override this function in high-availability programs to, say,
 free some memory if it cannot allocate memory, to use a special allocator,
 or even to sleep a while and retry until some memory is available.
 C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will
 override the flags completely if it is found in the environment. This is
 useful to try out specific backends to test their performance, or to work
 around bugs.
+=item C<EVFLAG_FORKCHECK>
+Instead of calling C<ev_default_fork> or C<ev_loop_fork> manually after
+a fork, you can also make libev check for a fork in each iteration by
+enabling this flag.
+This works by calling C<getpid ()> on every iteration of the loop,
+and thus this might slow down your event loop if you do a lot of loop
+iterations and little real work, but is usually not noticeable (on my
+Linux system for example, C<getpid> is actually a simple 5-insn sequence
+without a syscall and thus I<very> fast, but my Linux system also has
+C<pthread_atfork> which is even faster).
+The big advantage of this flag is that you can forget about fork (and
+forget about forgetting to tell libev about forking) when you use this
+flag.
+This flag setting cannot be overriden or specified in the C<LIBEV_FLAGS>
+environment variable.
 =item C<EVBACKEND_SELECT>  (value 1, portable select backend)
 This is your standard select(2) backend. Not I<completely> standard, as
 libev tries to roll its own fd_set with no limits on the number of fds,
 but if that fails, expect a fairly low limit on the number of fds when
 =item ev_loop_fork (loop)
 Like C<ev_default_fork>, but acts on an event loop created by
 C<ev_loop_new>. Yes, you have to call this on every allocated event loop
 after fork, and how you do this is entirely your own problem.
+=item unsigned int ev_loop_count (loop)
+Returns the count of loop iterations for the loop, which is identical to
+the number of times libev did poll for new events. It starts at C<0> and
+happily wraps around with enough iterations.
+This value can sometimes be useful as a generation counter of sorts (it
+"ticks" the number of loop iterations), as it roughly corresponds with
+C<ev_prepare> and C<ev_check> calls.
 =item unsigned int ev_backend (loop)
 Returns one of the C<EVBACKEND_*> flags indicating the event backend in
 use.
 =item ev_timer_again (loop)
 This will act as if the timer timed out and restart it again if it is
 repeating. The exact semantics are:
+If the timer is pending, its pending status is cleared.
-If the timer is started but nonrepeating, stop it.
+If the timer is started but nonrepeating, stop it (as if it timed out).
-If the timer is repeating, either start it if necessary (with the repeat
+If the timer is repeating, either start it if necessary (with the
-value), or reset the running timer to the repeat value.
+C<repeat> value), or reset the running timer to the C<repeat> value.
 This sounds a bit complicated, but here is a useful and typical
-example: Imagine you have a tcp connection and you want a so-called
+example: Imagine you have a tcp connection and you want a so-called idle
-idle timeout, that is, you want to be called when there have been,
+timeout, that is, you want to be called when there have been, say, 60
-say, 60 seconds of inactivity on the socket. The easiest way to do
+seconds of inactivity on the socket. The easiest way to do this is to
-this is to configure an C<ev_timer> with C<after>=C<repeat>=C<60> and calling
+configure an C<ev_timer> with a C<repeat> value of C<60> and then call
 C<ev_timer_again> each time you successfully read or write some data. If
 you go into an idle state where you do not expect data to travel on the
-socket, you can stop the timer, and again will automatically restart it if
+socket, you can C<ev_timer_stop> the timer, and C<ev_timer_again> will
-need be.
+automatically restart it if need be.
-You can also ignore the C<after> value and C<ev_timer_start> altogether
+That means you can ignore the C<after> value and C<ev_timer_start>
-and only ever use the C<repeat> value:
+altogether and only ever use the C<repeat> value and C<ev_timer_again>:
    ev_timer_init (timer, callback, 0., 5.);
    ev_timer_again (loop, timer);
    ...
    timer->again = 17.;
    ev_timer_again (loop, timer);
    ...
    timer->again = 10.;
    ev_timer_again (loop, timer);
-This is more efficient then stopping/starting the timer eahc time you want
+This is more slightly efficient then stopping/starting the timer each time
-to modify its timeout value.
+you want to modify its timeout value.
 =item ev_tstamp repeat [read-write]
 The current C<repeat> value. Will be used each time the watcher times out
 or C<ev_timer_again> is called and determines the next timeout (if any),
 The path does not need to exist: changing from "path exists" to "path does
 not exist" is a status change like any other. The condition "path does
 not exist" is signified by the C<st_nlink> field being zero (which is
 otherwise always forced to be at least one) and all the other fields of
 the stat buffer having unspecified contents.
+The path I<should> be absolute and I<must not> end in a slash. If it is
+relative and your working directory changes, the behaviour is undefined.
 Since there is no standard to do this, the portable implementation simply
 calls C<stat (2)> regularly on the path to see if it changed somehow. You
 can specify a recommended polling interval for this case. If you specify
 a polling interval of C<0> (highly recommended!) then a I<suitable,
   // create io watchers for each fd and a timer before blocking
   static void
   adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
   {
-    int timeout = 3600000;truct pollfd fds [nfd];
+    int timeout = 3600000;
+    struct pollfd fds [nfd];
     // actual code will need to loop here and realloc etc.
     adns_beforepoll (ads, fds, &nfd, &timeout, timeval_from (ev_time ()));
     /* the callback is illegal, but won't be called as we stop during check */
     ev_timer_init (&tw, 0, timeout * 1e-3);
 Similar to the other two macros, this gives you the value of the default
 loop, if multiple loops are supported ("ev loop default").
 =back
-Example: Declare and initialise a check watcher, working regardless of
+Example: Declare and initialise a check watcher, utilising the above
-wether multiple loops are supported or not.
+macros so it will work 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);
 =head1 EMBEDDING
 Libev can (and often is) directly embedded into host
 applications. Examples of applications that embed it include the Deliantra
   ev_vars.h
   ev_wrap.h
   ev_win32.c      required on win32 platforms only
-  ev_select.c     only when select backend is enabled (which is by default)
+  ev_select.c     only when select backend is enabled (which is enabled by default)
   ev_poll.c       only when poll backend is enabled (disabled by default)
   ev_epoll.c      only when the epoll backend is enabled (disabled by default)
   ev_kqueue.c     only when the kqueue backend is enabled (disabled by default)
   ev_port.c       only when the solaris port backend is enabled (disabled by default)
 interface) and F<EV.xs> (implementation) files. Only the F<EV.xs> file
 will be compiled. It is pretty complex because it provides its own header
 file.
 The usage in rxvt-unicode is simpler. It has a F<ev_cpp.h> header file
-that everybody includes and which overrides some autoconf choices:
+that everybody includes and which overrides some configure choices:
+  #define EV_MINIMAL 1
   #define EV_USE_POLL 0
   #define EV_MULTIPLICITY 0
-  #define EV_PERIODICS 0
+  #define EV_PERIODIC_ENABLE 0
+  #define EV_STAT_ENABLE 0
+  #define EV_FORK_ENABLE 0
   #define EV_CONFIG_H <config.h>
+  #define EV_MINPRI 0
+  #define EV_MAXPRI 0
   #include "ev++.h"
 And a F<ev_cpp.C> implementation file that contains libev proper and is compiled:

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.58 by root, Wed Nov 28 11:31:34 2007 UTC vs. Revision 1.66 by root, Mon Dec 3 13:41:25 2007 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.58 by root, Wed Nov 28 11:31:34 2007 UTC vs.
Revision 1.66 by root, Mon Dec 3 13:41:25 2007 UTC