| … | |
… | |
| 569 | kernel is more efficient (which says nothing about its actual speed, of |
569 | kernel is more efficient (which says nothing about its actual speed, of |
| 570 | course). While stopping, setting and starting an I/O watcher does never |
570 | course). While stopping, setting and starting an I/O watcher does never |
| 571 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
571 | cause an extra system call as with C<EVBACKEND_EPOLL>, it still adds up to |
| 572 | two event changes per incident. Support for C<fork ()> is very bad (you |
572 | two event changes per incident. Support for C<fork ()> is very bad (you |
| 573 | might have to leak fd's on fork, but it's more sane than epoll) and it |
573 | might have to leak fd's on fork, but it's more sane than epoll) and it |
| 574 | drops fds silently in similarly hard-to-detect cases |
574 | drops fds silently in similarly hard-to-detect cases. |
| 575 | |
575 | |
| 576 | This backend usually performs well under most conditions. |
576 | This backend usually performs well under most conditions. |
| 577 | |
577 | |
| 578 | While nominally embeddable in other event loops, this doesn't work |
578 | While nominally embeddable in other event loops, this doesn't work |
| 579 | everywhere, so you might need to test for this. And since it is broken |
579 | everywhere, so you might need to test for this. And since it is broken |
| … | |
… | |
| 1393 | transition between them will be described in more detail - and while these |
1393 | transition between them will be described in more detail - and while these |
| 1394 | rules might look complicated, they usually do "the right thing". |
1394 | rules might look complicated, they usually do "the right thing". |
| 1395 | |
1395 | |
| 1396 | =over 4 |
1396 | =over 4 |
| 1397 | |
1397 | |
| 1398 | =item initialiased |
1398 | =item initialised |
| 1399 | |
1399 | |
| 1400 | Before a watcher can be registered with the event loop it has to be |
1400 | Before a watcher can be registered with the event loop it has to be |
| 1401 | initialised. This can be done with a call to C<ev_TYPE_init>, or calls to |
1401 | initialised. This can be done with a call to C<ev_TYPE_init>, or calls to |
| 1402 | C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function. |
1402 | C<ev_init> followed by the watcher-specific C<ev_TYPE_set> function. |
| 1403 | |
1403 | |
