summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorroot <root>2008-01-09 04:15:39 +0000
committerroot <root>2008-01-09 04:15:39 +0000
commit906949bd4819e3a740ed7e0bdad5a6df62bfbb95 (patch)
treef573889a488459dbb934fa11904628352cf04602
parent9b47da80fe3aeb57d3340a633c83dd6e08bcc8e4 (diff)
*** empty log message ***
-rw-r--r--ev.pod9
1 files changed, 6 insertions, 3 deletions
diff --git a/ev.pod b/ev.pod
index 742177c..def18ac 100644
--- a/ev.pod
+++ b/ev.pod
@@ -405,6 +405,10 @@ file descriptor per loop iteration. For small and medium numbers of file
descriptors a "slow" C<EVBACKEND_SELECT> or C<EVBACKEND_POLL> backend
might perform better.
+On the positive side, ignoring the spurious readyness notifications, this
+backend actually performed to specification in all tests and is fully
+embeddable, which is a rare feat among the OS-specific backends.
+
=item C<EVBACKEND_ALL>
Try all backends (even potentially broken ones that wouldn't be tried
@@ -416,9 +420,8 @@ It is definitely not recommended to use this flag.
=back
If one or more of these are ored into the flags value, then only these
-backends will be tried (in the reverse order as given here). If none are
-specified, most compiled-in backend will be tried, usually in reverse
-order of their flag values :)
+backends will be tried (in the reverse order as listed here). If none are
+specified, all backends in C<ev_recommended_backends ()> will be tried.
The most typical usage is like this: