Browse Source

*** empty log message ***

master
Marc Alexander Lehmann 14 years ago
parent
commit
dd76aaa662
  1. 8
      ev.html
  2. 11
      ev.pod

8
ev.html

@ -6,7 +6,7 @@
<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="Mon Nov 12 09:32:26 2007" />
<meta name="created" content="Mon Nov 12 09:32:51 2007" />
<meta name="generator" content="Pod::Xhtml 1.57" />
<link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head>
<body>
@ -26,7 +26,7 @@
</ul>
</li>
<li><a href="#WATCHER_TYPES">WATCHER TYPES</a>
<ul><li><a href="#code_ev_io_code_is_my_file_descripto"><code>ev_io</code> - is my file descriptor readable or writable</a></li>
<ul><li><a href="#code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable</a></li>
<li><a href="#code_ev_timer_code_relative_and_opti"><code>ev_timer</code> - relative and optionally recurring timeouts</a></li>
<li><a href="#code_ev_periodic_code_to_cron_or_not"><code>ev_periodic</code> - to cron or not to cron it</a></li>
<li><a href="#code_ev_signal_code_signal_me_when_a"><code>ev_signal</code> - signal me when a signal gets signalled</a></li>
@ -428,8 +428,8 @@ have been omitted....</p>
information given in the last section.</p>
</div>
<h2 id="code_ev_io_code_is_my_file_descripto"><code>ev_io</code> - is my file descriptor readable or writable</h2>
<div id="code_ev_io_code_is_my_file_descripto-2">
<h2 id="code_ev_io_code_is_this_file_descrip"><code>ev_io</code> - is this file descriptor readable or writable</h2>
<div id="code_ev_io_code_is_this_file_descrip-2">
<p>I/O watchers check whether a file descriptor is readable or writable
in each iteration of the event loop (This behaviour is called
level-triggering because you keep receiving events as long as the

11
ev.pod

@ -406,7 +406,7 @@ have been omitted....
This section describes each watcher in detail, but will not repeat
information given in the last section.
=head2 C<ev_io> - is my file descriptor readable or writable
=head2 C<ev_io> - is this file descriptor readable or writable
I/O watchers check whether a file descriptor is readable or writable
in each iteration of the event loop (This behaviour is called
@ -546,7 +546,7 @@ time:
This doesn't mean there will always be 3600 seconds in between triggers,
but only that the the callback will be called when the system time shows a
full hour (UTC), or more correct, when the system time is evenly divisible
full hour (UTC), or more correctly, when the system time is evenly divisible
by 3600.
Another way to think about it (for the mathematically inclined) is that
@ -561,8 +561,11 @@ reschedule callback will be called with the watcher as first, and the
current time as second argument.
NOTE: I<This callback MUST NOT stop or destroy the periodic or any other
periodic watcher, ever, or make any event loop modificstions>. If you need
to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards.
periodic watcher, ever, or make any event loop modifications>. If you need
to stop it, return C<now + 1e30> (or so, fudge fudge) and stop it afterwards.
Also, I<<this callback must always return a time that is later than the
passed C<now> value >>. Not even C<now> itself will be ok.
Its prototype is c<ev_tstamp (*reschedule_cb)(struct ev_periodic *w,
ev_tstamp now)>, e.g.:

Loading…
Cancel
Save