ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.html
(Generate patch)

Comparing libev/ev.html (file contents):
Revision 1.69 by root, Fri Dec 7 20:19:16 2007 UTC vs.
Revision 1.74 by root, Sun Dec 9 19:42:57 2007 UTC

… …
4<head> 4<head>
5 <title>libev</title> 5 <title>libev</title>
6 <meta name="description" content="Pod documentation for libev" /> 6 <meta name="description" content="Pod documentation for libev" />
7 <meta name="inputfile" content="&lt;standard input&gt;" /> 7 <meta name="inputfile" content="&lt;standard input&gt;" />
8 <meta name="outputfile" content="&lt;standard output&gt;" /> 8 <meta name="outputfile" content="&lt;standard output&gt;" />
9 <meta name="created" content="Fri Dec 7 21:19:14 2007" /> 9 <meta name="created" content="Sun Dec 9 20:30:11 2007" />
10 <meta name="generator" content="Pod::Xhtml 1.57" /> 10 <meta name="generator" content="Pod::Xhtml 1.57" />
11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> 11<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
12<body> 12<body>
13<div class="pod"> 13<div class="pod">
14<!-- INDEX START --> 14<!-- INDEX START -->
… …
529one iteration of the loop. This is useful if you are waiting for some 529one iteration of the loop. This is useful if you are waiting for some
530external event in conjunction with something not expressible using other 530external event in conjunction with something not expressible using other
531libev watchers. However, a pair of <code>ev_prepare</code>/<code>ev_check</code> watchers is 531libev watchers. However, a pair of <code>ev_prepare</code>/<code>ev_check</code> watchers is
532usually a better approach for this kind of thing.</p> 532usually a better approach for this kind of thing.</p>
533 <p>Here are the gory details of what <code>ev_loop</code> does:</p> 533 <p>Here are the gory details of what <code>ev_loop</code> does:</p>
534<pre> - Before the first iteration, call any pending watchers.
534<pre> * If there are no active watchers (reference count is zero), return. 535 * If there are no active watchers (reference count is zero), return.
535 - Queue prepare watchers and then call all outstanding watchers. 536 - Queue all prepare watchers and then call all outstanding watchers.
536 - If we have been forked, recreate the kernel state. 537 - If we have been forked, recreate the kernel state.
537 - Update the kernel state with all outstanding changes. 538 - Update the kernel state with all outstanding changes.
538 - Update the &quot;event loop time&quot;. 539 - Update the &quot;event loop time&quot;.
539 - Calculate for how long to block. 540 - Calculate for how long to block.
540 - Block the process, waiting for any events. 541 - Block the process, waiting for any events.
… …
769 <dt>bool ev_is_pending (ev_TYPE *watcher)</dt> 770 <dt>bool ev_is_pending (ev_TYPE *watcher)</dt>
770 <dd> 771 <dd>
771 <p>Returns a true value iff the watcher is pending, (i.e. it has outstanding 772 <p>Returns a true value iff the watcher is pending, (i.e. it has outstanding
772events but its callback has not yet been invoked). As long as a watcher 773events but its callback has not yet been invoked). As long as a watcher
773is pending (but not active) you must not call an init function on it (but 774is pending (but not active) you must not call an init function on it (but
774<code>ev_TYPE_set</code> is safe) and you must make sure the watcher is available to 775<code>ev_TYPE_set</code> is safe), you must not change its priority, and you must
775libev (e.g. you cnanot <code>free ()</code> it).</p> 776make sure the watcher is available to libev (e.g. you cannot <code>free ()</code>
777it).</p>
776 </dd> 778 </dd>
777 <dt>callback ev_cb (ev_TYPE *watcher)</dt> 779 <dt>callback ev_cb (ev_TYPE *watcher)</dt>
778 <dd> 780 <dd>
779 <p>Returns the callback currently set on the watcher.</p> 781 <p>Returns the callback currently set on the watcher.</p>
780 </dd> 782 </dd>
… …
795invocation after new events have been received. This is useful, for 797invocation after new events have been received. This is useful, for
796example, to reduce latency after idling, or more often, to bind two 798example, to reduce latency after idling, or more often, to bind two
797watchers on the same event and make sure one is called first.</p> 799watchers on the same event and make sure one is called first.</p>
798 <p>If you need to suppress invocation when higher priority events are pending 800 <p>If you need to suppress invocation when higher priority events are pending
799you need to look at <code>ev_idle</code> watchers, which provide this functionality.</p> 801you need to look at <code>ev_idle</code> watchers, which provide this functionality.</p>
802 <p>You <i>must not</i> change the priority of a watcher as long as it is active or
803pending.</p>
800 <p>The default priority used by watchers when no priority has been set is 804 <p>The default priority used by watchers when no priority has been set is
801always <code>0</code>, which is supposed to not be too high and not be too low :).</p> 805always <code>0</code>, which is supposed to not be too high and not be too low :).</p>
802 <p>Setting a priority outside the range of <code>EV_MINPRI</code> to <code>EV_MAXPRI</code> is 806 <p>Setting a priority outside the range of <code>EV_MINPRI</code> to <code>EV_MAXPRI</code> is
803fine, as long as you do not mind that the priority value you query might 807fine, as long as you do not mind that the priority value you query might
804or might not have been adjusted to be within valid range.</p> 808or might not have been adjusted to be within valid range.</p>
809 </dd>
810 <dt>ev_invoke (loop, ev_TYPE *watcher, int revents)</dt>
811 <dd>
812 <p>Invoke the <code>watcher</code> with the given <code>loop</code> and <code>revents</code>. Neither
813<code>loop</code> nor <code>revents</code> need to be valid as long as the watcher callback
814can deal with that fact.</p>
815 </dd>
816 <dt>int ev_clear_pending (loop, ev_TYPE *watcher)</dt>
817 <dd>
818 <p>If the watcher is pending, this function returns clears its pending status
819and returns its <code>revents</code> bitset (as if its callback was invoked). If the
820watcher isn't pending it does nothing and returns <code>0</code>.</p>
805 </dd> 821 </dd>
806</dl> 822</dl>
807 823
808 824
809 825
… …
1081but on wallclock time (absolute time). You can tell a periodic watcher 1097but on wallclock time (absolute time). You can tell a periodic watcher
1082to trigger &quot;at&quot; some specific point in time. For example, if you tell a 1098to trigger &quot;at&quot; some specific point in time. For example, if you tell a
1083periodic watcher to trigger in 10 seconds (by specifiying e.g. <code>ev_now () 1099periodic watcher to trigger in 10 seconds (by specifiying e.g. <code>ev_now ()
1084+ 10.</code>) and then reset your system clock to the last year, then it will 1100+ 10.</code>) and then reset your system clock to the last year, then it will
1085take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger 1101take a year to trigger the event (unlike an <code>ev_timer</code>, which would trigger
1086roughly 10 seconds later and of course not if you reset your system time 1102roughly 10 seconds later).</p>
1087again).</p>
1088<p>They can also be used to implement vastly more complex timers, such as 1103<p>They can also be used to implement vastly more complex timers, such as
1089triggering an event on eahc midnight, local time.</p> 1104triggering an event on each midnight, local time or other, complicated,
1105rules.</p>
1090<p>As with timers, the callback is guarenteed to be invoked only when the 1106<p>As with timers, the callback is guarenteed to be invoked only when the
1091time (<code>at</code>) has been passed, but if multiple periodic timers become ready 1107time (<code>at</code>) has been passed, but if multiple periodic timers become ready
1092during the same loop iteration then order of execution is undefined.</p> 1108during the same loop iteration then order of execution is undefined.</p>
1093<dl> 1109<dl>
1094 <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt> 1110 <dt>ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)</dt>
… …
1096 <dd> 1112 <dd>
1097 <p>Lots of arguments, lets sort it out... There are basically three modes of 1113 <p>Lots of arguments, lets sort it out... There are basically three modes of
1098operation, and we will explain them from simplest to complex:</p> 1114operation, and we will explain them from simplest to complex:</p>
1099 <p> 1115 <p>
1100 <dl> 1116 <dl>
1101 <dt>* absolute timer (interval = reschedule_cb = 0)</dt> 1117 <dt>* absolute timer (at = time, interval = reschedule_cb = 0)</dt>
1102 <dd> 1118 <dd>
1103 <p>In this configuration the watcher triggers an event at the wallclock time 1119 <p>In this configuration the watcher triggers an event at the wallclock time
1104<code>at</code> and doesn't repeat. It will not adjust when a time jump occurs, 1120<code>at</code> and doesn't repeat. It will not adjust when a time jump occurs,
1105that is, if it is to be run at January 1st 2011 then it will run when the 1121that is, if it is to be run at January 1st 2011 then it will run when the
1106system time reaches or surpasses this time.</p> 1122system time reaches or surpasses this time.</p>
1107 </dd> 1123 </dd>
1108 <dt>* non-repeating interval timer (interval &gt; 0, reschedule_cb = 0)</dt> 1124 <dt>* non-repeating interval timer (at = offset, interval &gt; 0, reschedule_cb = 0)</dt>
1109 <dd> 1125 <dd>
1110 <p>In this mode the watcher will always be scheduled to time out at the next 1126 <p>In this mode the watcher will always be scheduled to time out at the next
1111<code>at + N * interval</code> time (for some integer N) and then repeat, regardless 1127<code>at + N * interval</code> time (for some integer N, which can also be negative)
1112of any time jumps.</p> 1128and then repeat, regardless of any time jumps.</p>
1113 <p>This can be used to create timers that do not drift with respect to system 1129 <p>This can be used to create timers that do not drift with respect to system
1114time:</p> 1130time:</p>
1115<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0); 1131<pre> ev_periodic_set (&amp;periodic, 0., 3600., 0);
1116 1132
1117</pre> 1133</pre>
… …
1120full hour (UTC), or more correctly, when the system time is evenly divisible 1136full hour (UTC), or more correctly, when the system time is evenly divisible
1121by 3600.</p> 1137by 3600.</p>
1122 <p>Another way to think about it (for the mathematically inclined) is that 1138 <p>Another way to think about it (for the mathematically inclined) is that
1123<code>ev_periodic</code> will try to run the callback in this mode at the next possible 1139<code>ev_periodic</code> will try to run the callback in this mode at the next possible
1124time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p> 1140time where <code>time = at (mod interval)</code>, regardless of any time jumps.</p>
1141 <p>For numerical stability it is preferable that the <code>at</code> value is near
1142<code>ev_now ()</code> (the current time), but there is no range requirement for
1143this value.</p>
1125 </dd> 1144 </dd>
1126 <dt>* manual reschedule mode (reschedule_cb = callback)</dt> 1145 <dt>* manual reschedule mode (at and interval ignored, reschedule_cb = callback)</dt>
1127 <dd> 1146 <dd>
1128 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being 1147 <p>In this mode the values for <code>interval</code> and <code>at</code> are both being
1129ignored. Instead, each time the periodic watcher gets scheduled, the 1148ignored. Instead, each time the periodic watcher gets scheduled, the
1130reschedule callback will be called with the watcher as first, and the 1149reschedule callback will be called with the watcher as first, and the
1131current time as second argument.</p> 1150current time as second argument.</p>
1132 <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher, 1151 <p>NOTE: <i>This callback MUST NOT stop or destroy any periodic watcher,
1133ever, or make any event loop modifications</i>. If you need to stop it, 1152ever, or make any event loop modifications</i>. If you need to stop it,
1134return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by 1153return <code>now + 1e30</code> (or so, fudge fudge) and stop it afterwards (e.g. by
1135starting a prepare watcher).</p> 1154starting an <code>ev_prepare</code> watcher, which is legal).</p>
1136 <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w, 1155 <p>Its prototype is <code>ev_tstamp (*reschedule_cb)(struct ev_periodic *w,
1137ev_tstamp now)</code>, e.g.:</p> 1156ev_tstamp now)</code>, e.g.:</p>
1138<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now) 1157<pre> static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)
1139 { 1158 {
1140 return now + 60.; 1159 return now + 60.;
… …
1160 <dd> 1179 <dd>
1161 <p>Simply stops and restarts the periodic watcher again. This is only useful 1180 <p>Simply stops and restarts the periodic watcher again. This is only useful
1162when you changed some parameters or the reschedule callback would return 1181when you changed some parameters or the reschedule callback would return
1163a different time than the last time it was called (e.g. in a crond like 1182a different time than the last time it was called (e.g. in a crond like
1164program when the crontabs have changed).</p> 1183program when the crontabs have changed).</p>
1184 </dd>
1185 <dt>ev_tstamp offset [read-write]</dt>
1186 <dd>
1187 <p>When repeating, this contains the offset value, otherwise this is the
1188absolute point in time (the <code>at</code> value passed to <code>ev_periodic_set</code>).</p>
1189 <p>Can be modified any time, but changes only take effect when the periodic
1190timer fires or <code>ev_periodic_again</code> is being called.</p>
1165 </dd> 1191 </dd>
1166 <dt>ev_tstamp interval [read-write]</dt> 1192 <dt>ev_tstamp interval [read-write]</dt>
1167 <dd> 1193 <dd>
1168 <p>The current interval value. Can be modified any time, but changes only 1194 <p>The current interval value. Can be modified any time, but changes only
1169take effect when the periodic timer fires or <code>ev_periodic_again</code> is being 1195take effect when the periodic timer fires or <code>ev_periodic_again</code> is being
… …
1468are ready to run (it's actually more complicated: it only runs coroutines 1494are ready to run (it's actually more complicated: it only runs coroutines
1469with priority higher than or equal to the event loop and one coroutine 1495with priority higher than or equal to the event loop and one coroutine
1470of lower priority, but only once, using idle watchers to keep the event 1496of lower priority, but only once, using idle watchers to keep the event
1471loop from blocking if lower-priority coroutines are active, thus mapping 1497loop from blocking if lower-priority coroutines are active, thus mapping
1472low-priority coroutines to idle/background tasks).</p> 1498low-priority coroutines to idle/background tasks).</p>
1499<p>It is recommended to give <code>ev_check</code> watchers highest (<code>EV_MAXPRI</code>)
1500priority, to ensure that they are being run before any other watchers
1501after the poll. Also, <code>ev_check</code> watchers (and <code>ev_prepare</code> watchers,
1502too) should not activate (&quot;feed&quot;) events into libev. While libev fully
1503supports this, they will be called before other <code>ev_check</code> watchers did
1504their job. As <code>ev_check</code> watchers are often used to embed other event
1505loops those other event loops might be in an unusable state until their
1506<code>ev_check</code> watcher ran (always remind yourself to coexist peacefully with
1507others).</p>
1473<dl> 1508<dl>
1474 <dt>ev_prepare_init (ev_prepare *, callback)</dt> 1509 <dt>ev_prepare_init (ev_prepare *, callback)</dt>
1475 <dt>ev_check_init (ev_check *, callback)</dt> 1510 <dt>ev_check_init (ev_check *, callback)</dt>
1476 <dd> 1511 <dd>
1477 <p>Initialises and configures the prepare or check watcher - they have no 1512 <p>Initialises and configures the prepare or check watcher - they have no
1478parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code> 1513parameters of any kind. There are <code>ev_prepare_set</code> and <code>ev_check_set</code>
1479macros, but using them is utterly, utterly and completely pointless.</p> 1514macros, but using them is utterly, utterly and completely pointless.</p>
1480 </dd> 1515 </dd>
1481</dl> 1516</dl>
1482<p>Example: To include a library such as adns, you would add IO watchers 1517<p>There are a number of principal ways to embed other event loops or modules
1483and a timeout watcher in a prepare handler, as required by libadns, and 1518into libev. Here are some ideas on how to include libadns into libev
1519(there is a Perl module named <code>EV::ADNS</code> that does this, which you could
1520use for an actually working example. Another Perl module named <code>EV::Glib</code>
1521embeds a Glib main context into libev, and finally, <code>Glib::EV</code> embeds EV
1522into the Glib event loop).</p>
1523<p>Method 1: Add IO watchers and a timeout watcher in a prepare handler,
1484in a check watcher, destroy them and call into libadns. What follows is 1524and in a check watcher, destroy them and call into libadns. What follows
1485pseudo-code only of course:</p> 1525is pseudo-code only of course. This requires you to either use a low
1526priority for the check watcher or use <code>ev_clear_pending</code> explicitly, as
1527the callbacks for the IO/timeout watchers might not have been called yet.</p>
1486<pre> static ev_io iow [nfd]; 1528<pre> static ev_io iow [nfd];
1487 static ev_timer tw; 1529 static ev_timer tw;
1488 1530
1489 static void 1531 static void
1490 io_cb (ev_loop *loop, ev_io *w, int revents) 1532 io_cb (ev_loop *loop, ev_io *w, int revents)
1491 { 1533 {
1492 // set the relevant poll flags
1493 // could also call adns_processreadable etc. here
1494 struct pollfd *fd = (struct pollfd *)w-&gt;data;
1495 if (revents &amp; EV_READ ) fd-&gt;revents |= fd-&gt;events &amp; POLLIN;
1496 if (revents &amp; EV_WRITE) fd-&gt;revents |= fd-&gt;events &amp; POLLOUT;
1497 } 1534 }
1498 1535
1499 // create io watchers for each fd and a timer before blocking 1536 // create io watchers for each fd and a timer before blocking
1500 static void 1537 static void
1501 adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents) 1538 adns_prepare_cb (ev_loop *loop, ev_prepare *w, int revents)
… …
1507 1544
1508 /* the callback is illegal, but won't be called as we stop during check */ 1545 /* the callback is illegal, but won't be called as we stop during check */
1509 ev_timer_init (&amp;tw, 0, timeout * 1e-3); 1546 ev_timer_init (&amp;tw, 0, timeout * 1e-3);
1510 ev_timer_start (loop, &amp;tw); 1547 ev_timer_start (loop, &amp;tw);
1511 1548
1512 // create on ev_io per pollfd 1549 // create one ev_io per pollfd
1513 for (int i = 0; i &lt; nfd; ++i) 1550 for (int i = 0; i &lt; nfd; ++i)
1514 { 1551 {
1515 ev_io_init (iow + i, io_cb, fds [i].fd, 1552 ev_io_init (iow + i, io_cb, fds [i].fd,
1516 ((fds [i].events &amp; POLLIN ? EV_READ : 0) 1553 ((fds [i].events &amp; POLLIN ? EV_READ : 0)
1517 | (fds [i].events &amp; POLLOUT ? EV_WRITE : 0))); 1554 | (fds [i].events &amp; POLLOUT ? EV_WRITE : 0)));
1518 1555
1519 fds [i].revents = 0; 1556 fds [i].revents = 0;
1520 iow [i].data = fds + i;
1521 ev_io_start (loop, iow + i); 1557 ev_io_start (loop, iow + i);
1522 } 1558 }
1523 } 1559 }
1524 1560
1525 // stop all watchers after blocking 1561 // stop all watchers after blocking
… …
1527 adns_check_cb (ev_loop *loop, ev_check *w, int revents) 1563 adns_check_cb (ev_loop *loop, ev_check *w, int revents)
1528 { 1564 {
1529 ev_timer_stop (loop, &amp;tw); 1565 ev_timer_stop (loop, &amp;tw);
1530 1566
1531 for (int i = 0; i &lt; nfd; ++i) 1567 for (int i = 0; i &lt; nfd; ++i)
1568 {
1569 // set the relevant poll flags
1570 // could also call adns_processreadable etc. here
1571 struct pollfd *fd = fds + i;
1572 int revents = ev_clear_pending (iow + i);
1573 if (revents &amp; EV_READ ) fd-&gt;revents |= fd-&gt;events &amp; POLLIN;
1574 if (revents &amp; EV_WRITE) fd-&gt;revents |= fd-&gt;events &amp; POLLOUT;
1575
1576 // now stop the watcher
1532 ev_io_stop (loop, iow + i); 1577 ev_io_stop (loop, iow + i);
1578 }
1533 1579
1534 adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop)); 1580 adns_afterpoll (adns, fds, nfd, timeval_from (ev_now (loop));
1581 }
1582
1583</pre>
1584<p>Method 2: This would be just like method 1, but you run <code>adns_afterpoll</code>
1585in the prepare watcher and would dispose of the check watcher.</p>
1586<p>Method 3: If the module to be embedded supports explicit event
1587notification (adns does), you can also make use of the actual watcher
1588callbacks, and only destroy/create the watchers in the prepare watcher.</p>
1589<pre> static void
1590 timer_cb (EV_P_ ev_timer *w, int revents)
1591 {
1592 adns_state ads = (adns_state)w-&gt;data;
1593 update_now (EV_A);
1594
1595 adns_processtimeouts (ads, &amp;tv_now);
1596 }
1597
1598 static void
1599 io_cb (EV_P_ ev_io *w, int revents)
1600 {
1601 adns_state ads = (adns_state)w-&gt;data;
1602 update_now (EV_A);
1603
1604 if (revents &amp; EV_READ ) adns_processreadable (ads, w-&gt;fd, &amp;tv_now);
1605 if (revents &amp; EV_WRITE) adns_processwriteable (ads, w-&gt;fd, &amp;tv_now);
1606 }
1607
1608 // do not ever call adns_afterpoll
1609
1610</pre>
1611<p>Method 4: Do not use a prepare or check watcher because the module you
1612want to embed is too inflexible to support it. Instead, youc na override
1613their poll function. The drawback with this solution is that the main
1614loop is now no longer controllable by EV. The <code>Glib::EV</code> module does
1615this.</p>
1616<pre> static gint
1617 event_poll_func (GPollFD *fds, guint nfds, gint timeout)
1618 {
1619 int got_events = 0;
1620
1621 for (n = 0; n &lt; nfds; ++n)
1622 // create/start io watcher that sets the relevant bits in fds[n] and increment got_events
1623
1624 if (timeout &gt;= 0)
1625 // create/start timer
1626
1627 // poll
1628 ev_loop (EV_A_ 0);
1629
1630 // stop timer again
1631 if (timeout &gt;= 0)
1632 ev_timer_stop (EV_A_ &amp;to);
1633
1634 // stop io watchers again - their callbacks should have set
1635 for (n = 0; n &lt; nfds; ++n)
1636 ev_io_stop (EV_A_ iow [n]);
1637
1638 return got_events;
1535 } 1639 }
1536 1640
1537 1641
1538 1642
1539 1643
… …
1806 ev::io iow; 1910 ev::io iow;
1807 iow.set &lt;myclass, &amp;myclass::io_cb&gt; (&amp;obj); 1911 iow.set &lt;myclass, &amp;myclass::io_cb&gt; (&amp;obj);
1808 1912
1809</pre> 1913</pre>
1810 </dd> 1914 </dd>
1811 <dt>w-&gt;set (void (*function)(watcher &amp;w, int), void *data = 0)</dt> 1915 <dt>w-&gt;set&lt;function&gt; (void *data = 0)</dt>
1812 <dd> 1916 <dd>
1813 <p>Also sets a callback, but uses a static method or plain function as 1917 <p>Also sets a callback, but uses a static method or plain function as
1814callback. The optional <code>data</code> argument will be stored in the watcher's 1918callback. The optional <code>data</code> argument will be stored in the watcher's
1815<code>data</code> member and is free for you to use.</p> 1919<code>data</code> member and is free for you to use.</p>
1920 <p>The prototype of the <code>function</code> must be <code>void (*)(ev::TYPE &amp;w, int)</code>.</p>
1816 <p>See the method-<code>set</code> above for more details.</p> 1921 <p>See the method-<code>set</code> above for more details.</p>
1922 <p>Example:</p>
1923<pre> static void io_cb (ev::io &amp;w, int revents) { }
1924 iow.set &lt;io_cb&gt; ();
1925
1926</pre>
1817 </dd> 1927 </dd>
1818 <dt>w-&gt;set (struct ev_loop *)</dt> 1928 <dt>w-&gt;set (struct ev_loop *)</dt>
1819 <dd> 1929 <dd>
1820 <p>Associates a different <code>struct ev_loop</code> with this watcher. You can only 1930 <p>Associates a different <code>struct ev_loop</code> with this watcher. You can only
1821do this when the watcher is inactive (and not pending either).</p> 1931do this when the watcher is inactive (and not pending either).</p>

Diff Legend

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