From e7279102641e8b208687717d64bf6e5e8ce9c446 Mon Sep 17 00:00:00 2001 From: Marc Alexander Lehmann Date: Tue, 25 Jun 2019 05:01:22 +0000 Subject: [PATCH] *** empty log message *** --- ev.pod | 18 +++++++++--------- 1 file changed, 9 insertions(+), 9 deletions(-) diff --git a/ev.pod b/ev.pod index 69308ac..fcef866 100644 --- a/ev.pod +++ b/ev.pod @@ -620,15 +620,15 @@ C. =item C (value 8, most BSD clones) -Kqueue deserves special mention, as at the time of this writing, it -was broken on all BSDs except NetBSD (usually it doesn't work reliably -with anything but sockets and pipes, except on Darwin, where of course -it's completely useless). Unlike epoll, however, whose brokenness -is by design, these kqueue bugs can (and eventually will) be fixed -without API changes to existing programs. For this reason it's not being -"auto-detected" unless you explicitly specify it in the flags (i.e. using -C) or libev was compiled on a known-to-be-good (-enough) -system like NetBSD. +Kqueue deserves special mention, as at the time this backend was +implemented, it was broken on all BSDs except NetBSD (usually it doesn't +work reliably with anything but sockets and pipes, except on Darwin, +where of course it's completely useless). Unlike epoll, however, whose +brokenness is by design, these kqueue bugs can be (and mostly have been) +fixed without API changes to existing programs. For this reason it's not +being "auto-detected" on all platforms unless you explicitly specify it +in the flags (i.e. using C) or libev was compiled on a +known-to-be-good (-enough) system like NetBSD. You still can embed kqueue into a normal poll or select backend and use it only for sockets (after having made sure that sockets work with kqueue on