*** empty log message ***

[software/libev.git] / README.embed

diff --git a/README.embed b/README.embed
index 5d60ee891b348b97505906535b23c72269b975c0..df5491a1d49a4f5e59611fe96ff63f72408078b1 100644 (file)
--- a/README.embed
+++ b/README.embed
@@ -61,10 +61,17 @@ FILESETS
         event.h
         event.c
 
+AUTOCONF SUPPORT
+
+    Instead of using EV_STANDALONE=1 and providing your config in whatever
+    way you want, you can also m4_include([libev.m4]) in your configure.ac
+    and leave EV_STANDALONE off. ev.c will then include "config.h" and
+    configure itself accordingly.
+
 PREPROCESSOR SYMBOLS
 
     Libev can be configured via a variety of preprocessor symbols you have to define
-    before including any of its files. The default is not to build for mulciplicity
+    before including any of its files. The default is not to build for multiplicity
     and only include the select backend.
 
     EV_STANDALONE
@@ -172,13 +179,15 @@ PREPROCESSOR SYMBOLS
 
     EV_CB_DECLARE(type)
     EV_CB_INVOKE(watcher,revents)
+    ev_set_cb(ev,cb)
 
        Can be used to change the callback member declaration in each
-       watcher, and the way callbacks are invoked. Must expand to a struct
-       member definition and a statement, respectively. See the ev.v
-       header file for their default definitions. One possible use for overriding
-       these is to avoid the ev_loop pointer as first argument in all cases, or
-       to use method calls instead of plain function calls in C++.
+       watcher, and the way callbacks are invoked and set. Must expand
+       to a struct member definition and a statement, respectively. See
+       the ev.v header file for their default definitions. One possible
+       use for overriding these is to avoid the ev_loop pointer as first
+       argument in all cases, or to use method calls instead of plain
+       function calls in C++.
 
 EXAMPLES