--- libev/ev.pod 2008/01/09 04:15:39 1.117 +++ libev/ev.pod 2008/01/10 06:00:55 1.118 @@ -262,6 +262,13 @@ If you don't know what event loop to use, use the one returned from this function. +The default loop is the only loop that can handle C and +C watchers, and to do this, it always registers a handler +for C. If this is a problem for your app you can either +create a dynamic loop with C that doesn't do that, or you +can simply overwrite the C signal handler I calling +C. + The flags argument can be used to specify special behaviour or specific backends to use, and is usually specified as C<0> (or C). @@ -2558,8 +2565,8 @@ =item EV_H The name of the F header file used to include it. The default if -undefined is C<"ev.h"> in F and F. This can be used to -virtually rename the F header file in case of conflicts. +undefined is C<"ev.h"> in F, F and F. This can be +used to virtually rename the F header file in case of conflicts. =item EV_CONFIG_H @@ -2570,7 +2577,7 @@ =item EV_EVENT_H Similarly to C, this macro can be used to override F's idea -of how the F header can be found, the dfeault is C<"event.h">. +of how the F header can be found, the default is C<"event.h">. =item EV_PROTOTYPES