From daa87a7bc949aa948f578145cc59ce65b902d888 Mon Sep 17 00:00:00 2001 From: root Date: Thu, 15 Nov 2012 01:39:45 +0000 Subject: *** empty log message *** --- ev.pod | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'ev.pod') diff --git a/ev.pod b/ev.pod index 1e28589..f43cc11 100644 --- a/ev.pod +++ b/ev.pod @@ -571,7 +571,7 @@ course). While stopping, setting and starting an I/O watcher does never cause an extra system call as with C, it still adds up to two event changes per incident. Support for C is very bad (you might have to leak fd's on fork, but it's more sane than epoll) and it -drops fds silently in similarly hard-to-detect cases +drops fds silently in similarly hard-to-detect cases. This backend usually performs well under most conditions. @@ -1395,7 +1395,7 @@ rules might look complicated, they usually do "the right thing". =over 4 -=item initialiased +=item initialised Before a watcher can be registered with the event loop it has to be initialised. This can be done with a call to C, or calls to -- cgit v1.2.3