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

Comparing libev/ev.html (file contents):
Revision 1.49 by root, Tue Nov 27 08:20:42 2007 UTC vs.
Revision 1.54 by root, Tue Nov 27 20:26:51 2007 UTC

 <head>
 	<title>libev</title>
 	<meta name="description" content="Pod documentation for libev" />
 	<meta name="inputfile" content="&lt;standard input&gt;" />
 	<meta name="outputfile" content="&lt;standard output&gt;" />
-	<meta name="created" content="Tue Nov 27 09:20:40 2007" />
+	<meta name="created" content="Tue Nov 27 21:26:46 2007" />
 	<meta name="generator" content="Pod::Xhtml 1.57" />
 <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
 <body>
 <div class="pod">
 <!-- INDEX START -->
 <h3 id="TOP">Index</h3>
 <ul><li><a href="#NAME">NAME</a></li>
 <li><a href="#SYNOPSIS">SYNOPSIS</a></li>
+<li><a href="#EXAMPLE_PROGRAM">EXAMPLE PROGRAM</a></li>
 <li><a href="#DESCRIPTION">DESCRIPTION</a></li>
 <li><a href="#FEATURES">FEATURES</a></li>
 <li><a href="#CONVENTIONS">CONVENTIONS</a></li>
 <li><a href="#TIME_REPRESENTATION">TIME REPRESENTATION</a></li>
 <li><a href="#GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</a></li>
 <li><a href="#code_ev_child_code_watch_out_for_pro"><code>ev_child</code> - watch out for process status changes</a></li>
 <li><a href="#code_ev_stat_code_did_the_file_attri"><code>ev_stat</code> - did the file attributes just change?</a></li>
 <li><a href="#code_ev_idle_code_when_you_ve_got_no"><code>ev_idle</code> - when you've got nothing better to do...</a></li>
 <li><a href="#code_ev_prepare_code_and_code_ev_che"><code>ev_prepare</code> and <code>ev_check</code> - customise your event loop!</a></li>
 <li><a href="#code_ev_embed_code_when_one_backend_"><code>ev_embed</code> - when one backend isn't enough...</a></li>
+<li><a href="#code_ev_fork_code_the_audacity_to_re"><code>ev_fork</code> - the audacity to resume the event loop after a fork</a></li>
 </ul>
 </li>
 <li><a href="#OTHER_FUNCTIONS">OTHER FUNCTIONS</a></li>
 <li><a href="#LIBEVENT_EMULATION">LIBEVENT EMULATION</a></li>
 <li><a href="#C_SUPPORT">C++ SUPPORT</a></li>
+<li><a href="#MACRO_MAGIC">MACRO MAGIC</a></li>
 <li><a href="#EMBEDDING">EMBEDDING</a>
 <ul><li><a href="#FILESETS">FILESETS</a>
 <ul><li><a href="#CORE_EVENT_LOOP">CORE EVENT LOOP</a></li>
 <li><a href="#LIBEVENT_COMPATIBILITY_API">LIBEVENT COMPATIBILITY API</a></li>
 <li><a href="#AUTOCONF_SUPPORT">AUTOCONF SUPPORT</a></li>
 <pre>  #include &lt;ev.h&gt;
 </pre>
 </div>
+<h1 id="EXAMPLE_PROGRAM">EXAMPLE PROGRAM</h1><p><a href="#TOP" class="toplink">Top</a></p>
+<div id="EXAMPLE_PROGRAM_CONTENT">
+<pre>  #include &lt;ev.h&gt;
+  ev_io stdin_watcher;
+  ev_timer timeout_watcher;
+  /* called when data readable on stdin */
+  static void
+  stdin_cb (EV_P_ struct ev_io *w, int revents)
+  {
+    /* puts (&quot;stdin ready&quot;); */
+    ev_io_stop (EV_A_ w); /* just a syntax example */
+    ev_unloop (EV_A_ EVUNLOOP_ALL); /* leave all loop calls */
+  }
+  static void
+  timeout_cb (EV_P_ struct ev_timer *w, int revents)
+  {
+    /* puts (&quot;timeout&quot;); */
+    ev_unloop (EV_A_ EVUNLOOP_ONE); /* leave one loop call */
+  }
+  int
+  main (void)
+  {
+    struct ev_loop *loop = ev_default_loop (0);
+    /* initialise an io watcher, then start it */
+    ev_io_init (&amp;stdin_watcher, stdin_cb, /*STDIN_FILENO*/ 0, EV_READ);
+    ev_io_start (loop, &amp;stdin_watcher);
+    /* simple non-repeating 5.5 second timeout */
+    ev_timer_init (&amp;timeout_watcher, timeout_cb, 5.5, 0.);
+    ev_timer_start (loop, &amp;timeout_watcher);
+    /* loop till timeout or data ready */
+    ev_loop (loop, 0);
+    return 0;
+  }
+</pre>
+</div>
 <h1 id="DESCRIPTION">DESCRIPTION</h1><p><a href="#TOP" class="toplink">Top</a></p>
 <div id="DESCRIPTION_CONTENT">
 <p>Libev is an event loop: you register interest in certain events (such as a
 file descriptor being readable or a timeout occuring), and it will manage
 these event sources and provide your program with events.</p>
 watcher.</p>
 </div>
 <h1 id="FEATURES">FEATURES</h1><p><a href="#TOP" class="toplink">Top</a></p>
 <div id="FEATURES_CONTENT">
-<p>Libev supports select, poll, the linux-specific epoll and the bsd-specific
+<p>Libev supports <code>select</code>, <code>poll</code>, the linux-specific <code>epoll</code>, the
-kqueue mechanisms for file descriptor events, relative timers, absolute
+bsd-specific <code>kqueue</code> and the solaris-specific event port mechanisms
-timers with customised rescheduling, signal events, process status change
+for file descriptor events (<code>ev_io</code>), relative timers (<code>ev_timer</code>),
-events (related to SIGCHLD), and event watchers dealing with the event
+absolute timers with customised rescheduling (<code>ev_periodic</code>), synchronous
-loop mechanism itself (idle, prepare and check watchers). It also is quite
+signals (<code>ev_signal</code>), process status change events (<code>ev_child</code>), and
+event watchers dealing with the event loop mechanism itself (<code>ev_idle</code>,
+<code>ev_embed</code>, <code>ev_prepare</code> and <code>ev_check</code> watchers) as well as
+file watchers (<code>ev_stat</code>) and even limited support for fork events
+(<code>ev_fork</code>).</p>
+<p>It also is quite fast (see this
-fast (see this <a href="http://libev.schmorp.de/bench.html">benchmark</a> comparing
+<a href="http://libev.schmorp.de/bench.html">benchmark</a> comparing it to libevent
-it to libevent for example).</p>
+for example).</p>
 </div>
 <h1 id="CONVENTIONS">CONVENTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
 <div id="CONVENTIONS_CONTENT">
-<p>Libev is very configurable. In this manual the default configuration
+<p>Libev is very configurable. In this manual the default configuration will
-will be described, which supports multiple event loops. For more info
+be described, which supports multiple event loops. For more info about
-about various configuration options please have a look at the file
+various configuration options please have a look at <strong>EMBED</strong> section in
-<cite>README.embed</cite> in the libev distribution. If libev was configured without
+this manual. If libev was configured without support for multiple event
-support for multiple event loops, then all functions taking an initial
+loops, then all functions taking an initial argument of name <code>loop</code>
-argument of name <code>loop</code> (which is always of type <code>struct ev_loop *</code>)
+(which is always of type <code>struct ev_loop *</code>) will not have this argument.</p>
-will not have this argument.</p>
 </div>
 <h1 id="TIME_REPRESENTATION">TIME REPRESENTATION</h1><p><a href="#TOP" class="toplink">Top</a></p>
 <div id="TIME_REPRESENTATION_CONTENT">
 <p>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 <code>ev_tstamp</code>, which is what you should use too. It usually aliases
 to the <code>double</code> type in C, and when you need to do any calculations on
 it, you should treat it as such.</p>
 </div>
 <h1 id="GLOBAL_FUNCTIONS">GLOBAL FUNCTIONS</h1><p><a href="#TOP" class="toplink">Top</a></p>
 <div id="GLOBAL_FUNCTIONS_CONTENT">
 <p>These functions can be called anytime, even before initialising the
 version of the library your program was compiled against.</p>
 		<p>Usually, it's a good idea to terminate if the major versions mismatch,
 as this indicates an incompatible change.  Minor versions are usually
 compatible to older versions, so a larger minor version alone is usually
 not a problem.</p>
-		<p>Example: make sure we haven't accidentally been linked against the wrong
+		<p>Example: Make sure we haven't accidentally been linked against the wrong
-version:</p>
+version.</p>
 <pre>  assert ((&quot;libev version mismatch&quot;,
            ev_version_major () == EV_VERSION_MAJOR
            &amp;&amp; ev_version_minor () &gt;= EV_VERSION_MINOR));
 </pre>
 might be supported on the current system, you would need to look at
 <code>ev_embeddable_backends () &amp; ev_supported_backends ()</code>, likewise for
 recommended ones.</p>
 		<p>See the description of <code>ev_embed</code> watchers for more info.</p>
 	</dd>
-	<dt>ev_set_allocator (void *(*cb)(void *ptr, long size))</dt>
+	<dt>ev_set_allocator (void *(*cb)(void *ptr, size_t size))</dt>
 	<dd>
-		<p>Sets the allocation function to use (the prototype is similar to the
+		<p>Sets the allocation function to use (the prototype and semantics are
-realloc C function, the semantics are identical). It is used to allocate
+identical to the realloc C function). It is used to allocate and free
-and free memory (no surprises here). If it returns zero when memory
+memory (no surprises here). If it returns zero when memory needs to be
-needs to be allocated, the library might abort or take some potentially
+allocated, the library might abort or take some potentially destructive
-destructive action. The default is your system realloc function.</p>
+action. The default is your system realloc function.</p>
 		<p>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.</p>
-		<p>Example: replace the libev allocator with one that waits a bit and then
+		<p>Example: Replace the libev allocator with one that waits a bit and then
-retries: better than mine).</p>
+retries).</p>
 <pre>   static void *
-   persistent_realloc (void *ptr, long size)
+   persistent_realloc (void *ptr, size_t size)
    {
      for (;;)
        {
          void *newptr = realloc (ptr, size);
 indicating the system call or subsystem causing the problem. If this
 callback is set, then libev will expect it to remedy the sitution, no
 matter what, when it returns. That is, libev will generally retry the
 requested operation, or, if the condition doesn't go away, do bad stuff
 (such as abort).</p>
-		<p>Example: do the same thing as libev does internally:</p>
+		<p>Example: This is basically the same thing that libev does internally, too.</p>
 <pre>   static void
    fatal_error (const char *msg)
    {
      perror (msg);
      abort ();
 	<dd>
 		<p>Similar to <code>ev_default_loop</code>, but always creates a new event loop that is
 always distinct from the default loop. Unlike the default loop, it cannot
 handle signal and child watchers, and attempts to do so will be greeted by
 undefined behaviour (or a failed assertion if assertions are enabled).</p>
-		<p>Example: try to create a event loop that uses epoll and nothing else.</p>
+		<p>Example: Try to create a event loop that uses epoll and nothing else.</p>
 <pre>  struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL | EVFLAG_NOENV);
   if (!epoller)
     fatal (&quot;no epoll found here, maybe it hides under your chair&quot;);
 </pre>
      be handled here by queueing them when their watcher gets executed.
    - If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
      were used, return, otherwise continue with step *.
 </pre>
-		<p>Example: queue some jobs and then loop until no events are outsanding
+		<p>Example: Queue some jobs and then loop until no events are outsanding
 anymore.</p>
 <pre>   ... queue jobs here, make sure they register event watchers as long
    ... as they still have work to do (even an idle watcher will do..)
    ev_loop (my_loop, 0);
    ... jobs done. yeah!
 example, libev itself uses this for its internal signal pipe: It is not
 visible to the libev user and should not keep <code>ev_loop</code> from exiting if
 no event watchers registered by it are active. It is also an excellent
 way to do this for generic recurring timers or from within third-party
 libraries. Just remember to <i>unref after start</i> and <i>ref before stop</i>.</p>
-		<p>Example: create a signal watcher, but keep it from keeping <code>ev_loop</code>
+		<p>Example: Create a signal watcher, but keep it from keeping <code>ev_loop</code>
 running when nothing else is active.</p>
-<pre>  struct dv_signal exitsig;
+<pre>  struct ev_signal exitsig;
   ev_signal_init (&amp;exitsig, sig_cb, SIGINT);
-  ev_signal_start (myloop, &amp;exitsig);
+  ev_signal_start (loop, &amp;exitsig);
-  evf_unref (myloop);
+  evf_unref (loop);
 </pre>
-		<p>Example: for some weird reason, unregister the above signal handler again.</p>
+		<p>Example: For some weird reason, unregister the above signal handler again.</p>
-<pre>  ev_ref (myloop);
+<pre>  ev_ref (loop);
-  ev_signal_stop (myloop, &amp;exitsig);
+  ev_signal_stop (loop, &amp;exitsig);
 </pre>
 	</dd>
 </dl>
 <code>ev_loop</code> has gathered them, but before it invokes any callbacks for any
 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 <code>ev_prepare</code> watcher might start an idle watcher to keep
 <code>ev_loop</code> from blocking).</p>
+	</dd>
+	<dt><code>EV_EMBED</code></dt>
+	<dd>
+		<p>The embedded event loop specified in the <code>ev_embed</code> watcher needs attention.</p>
+	</dd>
+	<dt><code>EV_FORK</code></dt>
+	<dd>
+		<p>The event loop has been resumed in the child process after fork (see
+<code>ev_fork</code>).</p>
 	</dd>
 	<dt><code>EV_ERROR</code></dt>
 	<dd>
 		<p>An unspecified error has occured, the watcher has been stopped. This might
 happen because the watcher could not be properly started because libev
 	<dt>int events [read-only]</dt>
 	<dd>
 		<p>The events being watched.</p>
 	</dd>
 </dl>
-<p>Example: call <code>stdin_readable_cb</code> when STDIN_FILENO has become, well
+<p>Example: Call <code>stdin_readable_cb</code> when STDIN_FILENO has become, well
 readable, but only once. Since it is likely line-buffered, you could
-attempt to read a whole line in the callback:</p>
+attempt to read a whole line in the callback.</p>
 <pre>  static void
   stdin_readable_cb (struct ev_loop *loop, struct ev_io *w, int revents)
   {
      ev_io_stop (loop, w);
     .. read from stdin here (or from w-&gt;fd) and haqndle any I/O errors
 		<p>The current <code>repeat</code> value. Will be used each time the watcher times out
 or <code>ev_timer_again</code> is called and determines the next timeout (if any),
 which is also when any modifications are taken into account.</p>
 	</dd>
 </dl>
-<p>Example: create a timer that fires after 60 seconds.</p>
+<p>Example: Create a timer that fires after 60 seconds.</p>
 <pre>  static void
   one_minute_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
   {
     .. one minute over, w is actually stopped right here
   }
   struct ev_timer mytimer;
   ev_timer_init (&amp;mytimer, one_minute_cb, 60., 0.);
   ev_timer_start (loop, &amp;mytimer);
 </pre>
-<p>Example: create a timeout timer that times out after 10 seconds of
+<p>Example: Create a timeout timer that times out after 10 seconds of
 inactivity.</p>
 <pre>  static void
   timeout_cb (struct ev_loop *loop, struct ev_timer *w, int revents)
   {
     .. ten seconds without any activity
 		<p>The current reschedule callback, or <code>0</code>, if this functionality is
 switched off. Can be changed any time, but changes only take effect when
 the periodic timer fires or <code>ev_periodic_again</code> is being called.</p>
 	</dd>
 </dl>
-<p>Example: call a callback every hour, or, more precisely, whenever the
+<p>Example: Call a callback every hour, or, more precisely, whenever the
 system clock is divisible by 3600. The callback invocation times have
 potentially a lot of jittering, but good long-term stability.</p>
 <pre>  static void
   clock_cb (struct ev_loop *loop, struct ev_io *w, int revents)
   {
   struct ev_periodic hourly_tick;
   ev_periodic_init (&amp;hourly_tick, clock_cb, 0., 3600., 0);
   ev_periodic_start (loop, &amp;hourly_tick);
 </pre>
-<p>Example: the same as above, but use a reschedule callback to do it:</p>
+<p>Example: The same as above, but use a reschedule callback to do it:</p>
 <pre>  #include &lt;math.h&gt;
   static ev_tstamp
   my_scheduler_cb (struct ev_periodic *w, ev_tstamp now)
   {
   }
   ev_periodic_init (&amp;hourly_tick, clock_cb, 0., 0., my_scheduler_cb);
 </pre>
-<p>Example: call a callback every hour, starting now:</p>
+<p>Example: Call a callback every hour, starting now:</p>
 <pre>  struct ev_periodic hourly_tick;
   ev_periodic_init (&amp;hourly_tick, clock_cb,
                     fmod (ev_now (loop), 3600.), 3600., 0);
   ev_periodic_start (loop, &amp;hourly_tick);
 	<dd>
 		<p>The process exit/trace status caused by <code>rpid</code> (see your systems
 <code>waitpid</code> and <code>sys/wait.h</code> documentation for details).</p>
 	</dd>
 </dl>
-<p>Example: try to exit cleanly on SIGINT and SIGTERM.</p>
+<p>Example: Try to exit cleanly on SIGINT and SIGTERM.</p>
 <pre>  static void
   sigint_cb (struct ev_loop *loop, struct ev_signal *w, int revents)
   {
     ev_unloop (loop, EVUNLOOP_ALL);
   }
 		<p>Initialises and configures the idle watcher - it has no parameters of any
 kind. There is a <code>ev_idle_set</code> macro, but using it is utterly pointless,
 believe me.</p>
 	</dd>
 </dl>
-<p>Example: dynamically allocate an <code>ev_idle</code>, start it, and in the
+<p>Example: Dynamically allocate an <code>ev_idle</code> watcher, start it, and in the
-callback, free it. Alos, use no error checking, as usual.</p>
+callback, free it. Also, use no error checking, as usual.</p>
 <pre>  static void
   idle_cb (struct ev_loop *loop, struct ev_idle *w, int revents)
   {
     free (w);
     // now do something you wanted to do when the program has
 apropriate way for embedded loops.</p>
 	</dd>
 	<dt>struct ev_loop *loop [read-only]</dt>
 	<dd>
 		<p>The embedded event loop.</p>
+	</dd>
+</dl>
+</div>
+<h2 id="code_ev_fork_code_the_audacity_to_re"><code>ev_fork</code> - the audacity to resume the event loop after a fork</h2>
+<div id="code_ev_fork_code_the_audacity_to_re-2">
+<p>Fork watchers are called when a <code>fork ()</code> was detected (usually because
+whoever is a good citizen cared to tell libev about it by calling
+<code>ev_default_fork</code> or <code>ev_loop_fork</code>). The invocation is done before the
+event loop blocks next and before <code>ev_check</code> watchers are being called,
+and only in the child after the fork. If whoever good citizen calling
+<code>ev_default_fork</code> cheats and calls it in the wrong process, the fork
+handlers will be invoked, too, of course.</p>
+<dl>
+	<dt>ev_fork_init (ev_signal *, callback)</dt>
+	<dd>
+		<p>Initialises and configures the fork watcher - it has no parameters of any
+kind. There is a <code>ev_fork_set</code> macro, but using it is utterly pointless,
+believe me.</p>
 	</dd>
 </dl>
     idle (this, &amp;myclass::idle_cb)
   {
     io.start (fd, ev::READ);
   }
+</pre>
+</div>
+<h1 id="MACRO_MAGIC">MACRO MAGIC</h1><p><a href="#TOP" class="toplink">Top</a></p>
+<div id="MACRO_MAGIC_CONTENT">
+<p>Libev can be compiled with a variety of options, the most fundemantal is
+<code>EV_MULTIPLICITY</code>. This option determines wether (most) functions and
+callbacks have an initial <code>struct ev_loop *</code> argument.</p>
+<p>To make it easier to write programs that cope with either variant, the
+following macros are defined:</p>
+<dl>
+	<dt><code>EV_A</code>, <code>EV_A_</code></dt>
+	<dd>
+		<p>This provides the loop <i>argument</i> for functions, if one is required (&quot;ev
+loop argument&quot;). The <code>EV_A</code> form is used when this is the sole argument,
+<code>EV_A_</code> is used when other arguments are following. Example:</p>
+<pre>  ev_unref (EV_A);
+  ev_timer_add (EV_A_ watcher);
+  ev_loop (EV_A_ 0);
+</pre>
+		<p>It assumes the variable <code>loop</code> of type <code>struct ev_loop *</code> is in scope,
+which is often provided by the following macro.</p>
+	</dd>
+	<dt><code>EV_P</code>, <code>EV_P_</code></dt>
+	<dd>
+		<p>This provides the loop <i>parameter</i> for functions, if one is required (&quot;ev
+loop parameter&quot;). The <code>EV_P</code> form is used when this is the sole parameter,
+<code>EV_P_</code> is used when other parameters are following. Example:</p>
+<pre>  // 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)
+</pre>
+		<p>It declares a parameter <code>loop</code> of type <code>struct ev_loop *</code>, quite
+suitable for use with <code>EV_A</code>.</p>
+	</dd>
+	<dt><code>EV_DEFAULT</code>, <code>EV_DEFAULT_</code></dt>
+	<dd>
+		<p>Similar to the other two macros, this gives you the value of the default
+loop, if multiple loops are supported (&quot;ev loop default&quot;).</p>
+	</dd>
+</dl>
+<p>Example: Declare and initialise a check watcher, working regardless of
+wether multiple loops are supported or not.</p>
+<pre>  static void
+  check_cb (EV_P_ ev_timer *w, int revents)
+  {
+    ev_check_stop (EV_A_ w);
+  }
+  ev_check check;
+  ev_check_init (&amp;check, check_cb);
+  ev_check_start (EV_DEFAULT_ &amp;check);
+  ev_loop (EV_DEFAULT_ 0);
 </pre>
 </div>
 <h1 id="EMBEDDING">EMBEDDING</h1><p><a href="#TOP" class="toplink">Top</a></p>
 <div id="EMBEDDING_CONTENT">
 	<dt>EV_STAT_ENABLE</dt>
 	<dd>
 		<p>If undefined or defined to be <code>1</code>, then stat watchers are supported. If
 defined to be <code>0</code>, then they are not.</p>
 	</dd>
+	<dt>EV_FORK_ENABLE</dt>
+	<dd>
+		<p>If undefined or defined to be <code>1</code>, then fork watchers are supported. If
+defined to be <code>0</code>, then they are not.</p>
+	</dd>
 	<dt>EV_MINIMAL</dt>
 	<dd>
 		<p>If you need to shave off some kilobytes of code at the expense of some
 speed, define this symbol to <code>1</code>. Currently only used for gcc to override
 some inlining decisions, saves roughly 30% codesize of amd64.</p>
+	</dd>
+	<dt>EV_PID_HASHSIZE</dt>
+	<dd>
+		<p><code>ev_child</code> watchers use a small hash table to distribute workload by
+pid. The default size is <code>16</code> (or <code>1</code> with <code>EV_MINIMAL</code>), usually more
+than enough. If you need to manage thousands of children you might want to
+increase this value.</p>
 	</dd>
 	<dt>EV_COMMON</dt>
 	<dd>
 		<p>By default, all watchers have a <code>void *data</code> member. By redefining
 this macro to a something else you can include more and other types of

Diff Legend

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

Comparing libev/ev.html (file contents): Revision 1.49 by root, Tue Nov 27 08:20:42 2007 UTC vs. Revision 1.54 by root, Tue Nov 27 20:26:51 2007 UTC

Diff Legend

Comparing libev/ev.html (file contents):
Revision 1.49 by root, Tue Nov 27 08:20:42 2007 UTC vs.
Revision 1.54 by root, Tue Nov 27 20:26:51 2007 UTC