diff options
| -rw-r--r-- | ev.3 | 6 | ||||
| -rw-r--r-- | ev.c | 2 | ||||
| -rw-r--r-- | ev.html | 8 | ||||
| -rw-r--r-- | ev.pod | 6 |
4 files changed, 11 insertions, 11 deletions
@@ -1042,7 +1042,7 @@ it is best to always use non-blocking I/O: An extra \f(CW\*(C`read\*(C'\fR(2) re .PP If you cannot run the fd in non-blocking mode (for example you should not play around with an Xlib connection), then you have to seperately re-test -wether a file descriptor is really ready with a known-to-be good interface +whether a file descriptor is really ready with a known-to-be good interface such as poll (fortunately in our Xlib example, Xlib already does this on its own, so its quite safe to use). .IP "ev_io_init (ev_io *, callback, int fd, int events)" 4 @@ -1993,7 +1993,7 @@ the constructor. .SH "MACRO MAGIC" .IX Header "MACRO MAGIC" Libev can be compiled with a variety of options, the most fundemantal is -\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines wether (most) functions and +\&\f(CW\*(C`EV_MULTIPLICITY\*(C'\fR. This option determines whether (most) functions and callbacks have an initial \f(CW\*(C`struct ev_loop *\*(C'\fR argument. .PP To make it easier to write programs that cope with either variant, the @@ -2039,7 +2039,7 @@ Similar to the other two macros, this gives you the value of the default loop, if multiple loops are supported (\*(L"ev loop default\*(R"). .PP Example: Declare and initialise a check watcher, utilising the above -macros so it will work regardless of wether multiple loops are supported +macros so it will work regardless of whether multiple loops are supported or not. .PP .Vb 5 @@ -1268,7 +1268,7 @@ periodics_reschedule (EV_P) void inline_size idle_reify (EV_P) { - if (expect_false (!idleall)) + if (expect_false (idleall)) { int pri; @@ -6,7 +6,7 @@ <meta name="description" content="Pod documentation for libev" /> <meta name="inputfile" content="<standard input>" /> <meta name="outputfile" content="<standard output>" /> - <meta name="created" content="Fri Dec 7 17:49:47 2007" /> + <meta name="created" content="Fri Dec 7 19:03:06 2007" /> <meta name="generator" content="Pod::Xhtml 1.57" /> <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> <body> @@ -919,7 +919,7 @@ it is best to always use non-blocking I/O: An extra <code>read</code>(2) returni <code>EAGAIN</code> is far preferable to a program hanging until some data arrives.</p> <p>If you cannot run the fd in non-blocking mode (for example you should not play around with an Xlib connection), then you have to seperately re-test -wether a file descriptor is really ready with a known-to-be good interface +whether a file descriptor is really ready with a known-to-be good interface such as poll (fortunately in our Xlib example, Xlib already does this on its own, so its quite safe to use).</p> <dl> @@ -1834,7 +1834,7 @@ the constructor.</p> <h1 id="MACRO_MAGIC">MACRO MAGIC</h1> <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 +<code>EV_MULTIPLICITY</code>. This option determines whether (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> @@ -1874,7 +1874,7 @@ loop, if multiple loops are supported ("ev loop default").</p> </dd> </dl> <p>Example: Declare and initialise a check watcher, utilising the above -macros so it will work regardless of wether multiple loops are supported +macros so it will work regardless of whether multiple loops are supported or not.</p> <pre> static void check_cb (EV_P_ ev_timer *w, int revents) @@ -885,7 +885,7 @@ C<EAGAIN> is far preferable to a program hanging until some data arrives. If you cannot run the fd in non-blocking mode (for example you should not play around with an Xlib connection), then you have to seperately re-test -wether a file descriptor is really ready with a known-to-be good interface +whether a file descriptor is really ready with a known-to-be good interface such as poll (fortunately in our Xlib example, Xlib already does this on its own, so its quite safe to use). @@ -1846,7 +1846,7 @@ the constructor. =head1 MACRO MAGIC Libev can be compiled with a variety of options, the most fundemantal is -C<EV_MULTIPLICITY>. This option determines wether (most) functions and +C<EV_MULTIPLICITY>. This option determines whether (most) functions and callbacks have an initial C<struct ev_loop *> argument. To make it easier to write programs that cope with either variant, the @@ -1890,7 +1890,7 @@ loop, if multiple loops are supported ("ev loop default"). =back Example: Declare and initialise a check watcher, utilising the above -macros so it will work regardless of wether multiple loops are supported +macros so it will work regardless of whether multiple loops are supported or not. static void |