diff options
author | root <root> | 2007-11-24 16:33:23 +0000 |
---|---|---|
committer | root <root> | 2007-11-24 16:33:23 +0000 |
commit | 97710f65c4339600b822e15e7e78841ae445f0f5 (patch) | |
tree | e9024be6e457c36a4b18a6cd2eb98f4dbc0cab40 | |
parent | 9ed25a080c823727fa23609c493b3f77585581e2 (diff) |
*** empty log message ***
-rw-r--r-- | ev.3 | 8 | ||||
-rw-r--r-- | ev.html | 10 | ||||
-rw-r--r-- | ev.pod | 8 |
3 files changed, 13 insertions, 13 deletions
@@ -1601,7 +1601,7 @@ in your include path (e.g. in libev/ when using \-Ilibev): .Ve .PP .Vb 5 -\& ev_select.c only when select backend is enabled (which is is by default) +\& ev_select.c only when select backend is enabled (which is by default) \& ev_poll.c only when poll backend is enabled (disabled by default) \& ev_epoll.c only when the epoll backend is enabled (disabled by default) \& ev_kqueue.c only when the kqueue backend is enabled (disabled by default) @@ -1609,7 +1609,7 @@ in your include path (e.g. in libev/ when using \-Ilibev): .Ve .PP \&\fIev.c\fR includes the backend files directly when enabled, so you only need -to compile a single file. +to compile this single file. .PP \fI\s-1LIBEVENT\s0 \s-1COMPATIBILITY\s0 \s-1API\s0\fR .IX Subsection "LIBEVENT COMPATIBILITY API" @@ -1640,8 +1640,8 @@ You need the following additional files for this: .PP Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your config in whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your -\&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR off. \fIev.c\fR will then include -\&\fIconfig.h\fR and configure itself accordingly. +\&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then +include \fIconfig.h\fR and configure itself accordingly. .PP For this of course you need the m4 file: .PP @@ -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="Sat Nov 24 17:31:33 2007" /> + <meta name="created" content="Sat Nov 24 17:33:21 2007" /> <meta name="generator" content="Pod::Xhtml 1.57" /> <link rel="stylesheet" href="http://res.tst.eu/pod.css"/></head> <body> @@ -1471,7 +1471,7 @@ in your include path (e.g. in libev/ when using -Ilibev):</p> ev_win32.c required on win32 platforms only - ev_select.c only when select backend is enabled (which is is by default) + ev_select.c only when select backend is enabled (which is by default) ev_poll.c only when poll backend is enabled (disabled by default) ev_epoll.c only when the epoll backend is enabled (disabled by default) ev_kqueue.c only when the kqueue backend is enabled (disabled by default) @@ -1479,7 +1479,7 @@ in your include path (e.g. in libev/ when using -Ilibev):</p> </pre> <p><cite>ev.c</cite> includes the backend files directly when enabled, so you only need -to compile a single file.</p> +to compile this single file.</p> </div> <h3 id="LIBEVENT_COMPATIBILITY_API">LIBEVENT COMPATIBILITY API</h3> @@ -1504,8 +1504,8 @@ to compile a single file.</p> <div id="AUTOCONF_SUPPORT_CONTENT"> <p>Instead of using <code>EV_STANDALONE=1</code> and providing your config in whatever way you want, you can also <code>m4_include([libev.m4])</code> in your -<cite>configure.ac</cite> and leave <code>EV_STANDALONE</code> off. <cite>ev.c</cite> will then include -<cite>config.h</cite> and configure itself accordingly.</p> +<cite>configure.ac</cite> and leave <code>EV_STANDALONE</code> undefined. <cite>ev.c</cite> will then +include <cite>config.h</cite> and configure itself accordingly.</p> <p>For this of course you need the m4 file:</p> <pre> libev.m4 @@ -1471,14 +1471,14 @@ in your include path (e.g. in libev/ when using -Ilibev): ev_win32.c required on win32 platforms only - ev_select.c only when select backend is enabled (which is is by default) + ev_select.c only when select backend is enabled (which is by default) ev_poll.c only when poll backend is enabled (disabled by default) ev_epoll.c only when the epoll backend is enabled (disabled by default) ev_kqueue.c only when the kqueue backend is enabled (disabled by default) ev_port.c only when the solaris port backend is enabled (disabled by default) F<ev.c> includes the backend files directly when enabled, so you only need -to compile a single file. +to compile this single file. =head3 LIBEVENT COMPATIBILITY API @@ -1501,8 +1501,8 @@ You need the following additional files for this: Instead of using C<EV_STANDALONE=1> and providing your config in whatever way you want, you can also C<m4_include([libev.m4])> in your -F<configure.ac> and leave C<EV_STANDALONE> off. F<ev.c> will then include -F<config.h> and configure itself accordingly. +F<configure.ac> and leave C<EV_STANDALONE> undefined. F<ev.c> will then +include F<config.h> and configure itself accordingly. For this of course you need the m4 file: |