diff options
author | root <root> | 2007-12-07 18:09:38 +0000 |
---|---|---|
committer | root <root> | 2007-12-07 18:09:38 +0000 |
commit | 554d51b833eb2ed17c9d07a8362c2dcd565139f9 (patch) | |
tree | a1ee7a43f1d043d2399ecb02a651095f3771747d /ev.pod | |
parent | c3a3f33d0d4ad477f0b40f4ea649d6ac523a45fa (diff) |
*** empty log message ***rel-1_71
Diffstat (limited to 'ev.pod')
-rw-r--r-- | ev.pod | 6 |
1 files changed, 3 insertions, 3 deletions
@@ -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 |