ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/libev/ev.3
(Generate patch)

Comparing libev/ev.3 (file contents):
Revision 1.98 by root, Thu Feb 28 02:17:11 2013 UTC vs.
Revision 1.103 by root, Fri May 1 17:23:34 2015 UTC

1.\" Automatically generated by Pod::Man 2.25 (Pod::Simple 3.16) 1.\" Automatically generated by Pod::Man 2.28 (Pod::Simple 3.28)
2.\" 2.\"
3.\" Standard preamble: 3.\" Standard preamble:
4.\" ======================================================================== 4.\" ========================================================================
5.de Sp \" Vertical space (when we can't use .PP) 5.de Sp \" Vertical space (when we can't use .PP)
6.if t .sp .5v 6.if t .sp .5v
… …
36.el\{\ 36.el\{\
37. ds -- \|\(em\| 37. ds -- \|\(em\|
38. ds PI \(*p 38. ds PI \(*p
39. ds L" `` 39. ds L" ``
40. ds R" '' 40. ds R" ''
41. ds C`
42. ds C'
41'br\} 43'br\}
42.\" 44.\"
43.\" Escape single quotes in literal strings from groff's Unicode transform. 45.\" Escape single quotes in literal strings from groff's Unicode transform.
44.ie \n(.g .ds Aq \(aq 46.ie \n(.g .ds Aq \(aq
45.el .ds Aq ' 47.el .ds Aq '
46.\" 48.\"
47.\" If the F register is turned on, we'll generate index entries on stderr for 49.\" If the F register is turned on, we'll generate index entries on stderr for
48.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index 50.\" titles (.TH), headers (.SH), subsections (.SS), items (.Ip), and index
49.\" entries marked with X<> in POD. Of course, you'll have to process the 51.\" entries marked with X<> in POD. Of course, you'll have to process the
50.\" output yourself in some meaningful fashion. 52.\" output yourself in some meaningful fashion.
51.ie \nF \{\ 53.\"
54.\" Avoid warning from groff about undefined register 'F'.
52. de IX 55.de IX
53. tm Index:\\$1\t\\n%\t"\\$2"
54.. 56..
55. nr % 0 57.nr rF 0
56. rr F 58.if \n(.g .if rF .nr rF 1
59.if (\n(rF:(\n(.g==0)) \{
60. if \nF \{
61. de IX
62. tm Index:\\$1\t\\n%\t"\\$2"
63..
64. if !\nF==2 \{
65. nr % 0
66. nr F 2
67. \}
68. \}
57.\} 69.\}
58.el \{\ 70.rr rF
59. de IX
60..
61.\}
62.\" 71.\"
63.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2). 72.\" Accent mark definitions (@(#)ms.acc 1.5 88/02/08 SMI; from UCB 4.2).
64.\" Fear. Run. Save yourself. No user-serviceable parts. 73.\" Fear. Run. Save yourself. No user-serviceable parts.
65. \" fudge factors for nroff and troff 74. \" fudge factors for nroff and troff
66.if n \{\ 75.if n \{\
… …
122.\} 131.\}
123.rm #[ #] #H #V #F C 132.rm #[ #] #H #V #F C
124.\" ======================================================================== 133.\" ========================================================================
125.\" 134.\"
126.IX Title "LIBEV 3" 135.IX Title "LIBEV 3"
127.TH LIBEV 3 "2013-02-28" "libev-4.11" "libev - high performance full featured event loop" 136.TH LIBEV 3 "2015-05-01" "libev-4.19" "libev - high performance full featured event loop"
128.\" For nroff, turn off justification. Always turn off hyphenation; it makes 137.\" For nroff, turn off justification. Always turn off hyphenation; it makes
129.\" way too many mistakes in technical documents. 138.\" way too many mistakes in technical documents.
130.if n .ad l 139.if n .ad l
131.nh 140.nh
132.SH "NAME" 141.SH "NAME"
… …
134.SH "SYNOPSIS" 143.SH "SYNOPSIS"
135.IX Header "SYNOPSIS" 144.IX Header "SYNOPSIS"
136.Vb 1 145.Vb 1
137\& #include <ev.h> 146\& #include <ev.h>
138.Ve 147.Ve
139.SS "\s-1EXAMPLE\s0 \s-1PROGRAM\s0" 148.SS "\s-1EXAMPLE PROGRAM\s0"
140.IX Subsection "EXAMPLE PROGRAM" 149.IX Subsection "EXAMPLE PROGRAM"
141.Vb 2 150.Vb 2
142\& // a single header file is required 151\& // a single header file is required
143\& #include <ev.h> 152\& #include <ev.h>
144\& 153\&
… …
212throughout this document. 221throughout this document.
213.SH "WHAT TO READ WHEN IN A HURRY" 222.SH "WHAT TO READ WHEN IN A HURRY"
214.IX Header "WHAT TO READ WHEN IN A HURRY" 223.IX Header "WHAT TO READ WHEN IN A HURRY"
215This manual tries to be very detailed, but unfortunately, this also makes 224This manual tries to be very detailed, but unfortunately, this also makes
216it very long. If you just want to know the basics of libev, I suggest 225it very long. If you just want to know the basics of libev, I suggest
217reading \*(L"\s-1ANATOMY\s0 \s-1OF\s0 A \s-1WATCHER\s0\*(R", then the \*(L"\s-1EXAMPLE\s0 \s-1PROGRAM\s0\*(R" above and 226reading \*(L"\s-1ANATOMY OF A WATCHER\*(R"\s0, then the \*(L"\s-1EXAMPLE PROGRAM\*(R"\s0 above and
218look up the missing functions in \*(L"\s-1GLOBAL\s0 \s-1FUNCTIONS\s0\*(R" and the \f(CW\*(C`ev_io\*(C'\fR and 227look up the missing functions in \*(L"\s-1GLOBAL FUNCTIONS\*(R"\s0 and the \f(CW\*(C`ev_io\*(C'\fR and
219\&\f(CW\*(C`ev_timer\*(C'\fR sections in \*(L"\s-1WATCHER\s0 \s-1TYPES\s0\*(R". 228\&\f(CW\*(C`ev_timer\*(C'\fR sections in \*(L"\s-1WATCHER TYPES\*(R"\s0.
220.SH "ABOUT LIBEV" 229.SH "ABOUT LIBEV"
221.IX Header "ABOUT LIBEV" 230.IX Header "ABOUT LIBEV"
222Libev is an event loop: you register interest in certain events (such as a 231Libev is an event loop: you register interest in certain events (such as a
223file descriptor being readable or a timeout occurring), and it will manage 232file descriptor being readable or a timeout occurring), and it will manage
224these event sources and provide your program with events. 233these event sources and provide your program with events.
… …
255more info about various configuration options please have a look at 264more info about various configuration options please have a look at
256\&\fB\s-1EMBED\s0\fR section in this manual. If libev was configured without support 265\&\fB\s-1EMBED\s0\fR section in this manual. If libev was configured without support
257for multiple event loops, then all functions taking an initial argument of 266for multiple event loops, then all functions taking an initial argument of
258name \f(CW\*(C`loop\*(C'\fR (which is always of type \f(CW\*(C`struct ev_loop *\*(C'\fR) will not have 267name \f(CW\*(C`loop\*(C'\fR (which is always of type \f(CW\*(C`struct ev_loop *\*(C'\fR) will not have
259this argument. 268this argument.
260.SS "\s-1TIME\s0 \s-1REPRESENTATION\s0" 269.SS "\s-1TIME REPRESENTATION\s0"
261.IX Subsection "TIME REPRESENTATION" 270.IX Subsection "TIME REPRESENTATION"
262Libev represents time as a single floating point number, representing 271Libev represents time as a single floating point number, representing
263the (fractional) number of seconds since the (\s-1POSIX\s0) epoch (in practice 272the (fractional) number of seconds since the (\s-1POSIX\s0) epoch (in practice
264somewhere near the beginning of 1970, details are complicated, don't 273somewhere near the beginning of 1970, details are complicated, don't
265ask). This type is called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use 274ask). This type is called \f(CW\*(C`ev_tstamp\*(C'\fR, which is what you should use
… …
514.IX Item "EVFLAG_NOENV" 523.IX Item "EVFLAG_NOENV"
515If this flag bit is or'ed into the flag value (or the program runs setuid 524If this flag bit is or'ed into the flag value (or the program runs setuid
516or setgid) then libev will \fInot\fR look at the environment variable 525or setgid) then libev will \fInot\fR look at the environment variable
517\&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will 526\&\f(CW\*(C`LIBEV_FLAGS\*(C'\fR. Otherwise (the default), this environment variable will
518override the flags completely if it is found in the environment. This is 527override the flags completely if it is found in the environment. This is
519useful to try out specific backends to test their performance, or to work 528useful to try out specific backends to test their performance, to work
520around bugs. 529around bugs, or to make libev threadsafe (accessing environment variables
530cannot be done in a threadsafe way, but usually it works if no other
531thread modifies them).
521.ie n .IP """EVFLAG_FORKCHECK""" 4 532.ie n .IP """EVFLAG_FORKCHECK""" 4
522.el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4 533.el .IP "\f(CWEVFLAG_FORKCHECK\fR" 4
523.IX Item "EVFLAG_FORKCHECK" 534.IX Item "EVFLAG_FORKCHECK"
524Instead of calling \f(CW\*(C`ev_loop_fork\*(C'\fR manually after a fork, you can also 535Instead of calling \f(CW\*(C`ev_loop_fork\*(C'\fR manually after a fork, you can also
525make libev check for a fork in each iteration by enabling this flag. 536make libev check for a fork in each iteration by enabling this flag.
… …
572\&\f(CW\*(C`sigprocmask\*(C'\fR, whose behaviour is officially unspecified. 583\&\f(CW\*(C`sigprocmask\*(C'\fR, whose behaviour is officially unspecified.
573.Sp 584.Sp
574This flag's behaviour will become the default in future versions of libev. 585This flag's behaviour will become the default in future versions of libev.
575.ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4 586.ie n .IP """EVBACKEND_SELECT"" (value 1, portable select backend)" 4
576.el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4 587.el .IP "\f(CWEVBACKEND_SELECT\fR (value 1, portable select backend)" 4
577.IX Item "EVBACKEND_SELECT (value 1, portable select backend)" 588.IX Item "EVBACKEND_SELECT (value 1, portable select backend)"
578This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as 589This is your standard \fIselect\fR\|(2) backend. Not \fIcompletely\fR standard, as
579libev tries to roll its own fd_set with no limits on the number of fds, 590libev tries to roll its own fd_set with no limits on the number of fds,
580but if that fails, expect a fairly low limit on the number of fds when 591but if that fails, expect a fairly low limit on the number of fds when
581using this backend. It doesn't scale too well (O(highest_fd)), but its 592using this backend. It doesn't scale too well (O(highest_fd)), but its
582usually the fastest backend for a low number of (low-numbered :) fds. 593usually the fastest backend for a low number of (low-numbered :) fds.
… …
591This backend maps \f(CW\*(C`EV_READ\*(C'\fR to the \f(CW\*(C`readfds\*(C'\fR set and \f(CW\*(C`EV_WRITE\*(C'\fR to the 602This backend maps \f(CW\*(C`EV_READ\*(C'\fR to the \f(CW\*(C`readfds\*(C'\fR set and \f(CW\*(C`EV_WRITE\*(C'\fR to the
592\&\f(CW\*(C`writefds\*(C'\fR set (and to work around Microsoft Windows bugs, also onto the 603\&\f(CW\*(C`writefds\*(C'\fR set (and to work around Microsoft Windows bugs, also onto the
593\&\f(CW\*(C`exceptfds\*(C'\fR set on that platform). 604\&\f(CW\*(C`exceptfds\*(C'\fR set on that platform).
594.ie n .IP """EVBACKEND_POLL"" (value 2, poll backend, available everywhere except on windows)" 4 605.ie n .IP """EVBACKEND_POLL"" (value 2, poll backend, available everywhere except on windows)" 4
595.el .IP "\f(CWEVBACKEND_POLL\fR (value 2, poll backend, available everywhere except on windows)" 4 606.el .IP "\f(CWEVBACKEND_POLL\fR (value 2, poll backend, available everywhere except on windows)" 4
596.IX Item "EVBACKEND_POLL (value 2, poll backend, available everywhere except on windows)" 607.IX Item "EVBACKEND_POLL (value 2, poll backend, available everywhere except on windows)"
597And this is your standard \fIpoll\fR\|(2) backend. It's more complicated 608And this is your standard \fIpoll\fR\|(2) backend. It's more complicated
598than select, but handles sparse fds better and has no artificial 609than select, but handles sparse fds better and has no artificial
599limit on the number of fds you can use (except it will slow down 610limit on the number of fds you can use (except it will slow down
600considerably with a lot of inactive fds). It scales similarly to select, 611considerably with a lot of inactive fds). It scales similarly to select,
601i.e. O(total_fds). See the entry for \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR, above, for 612i.e. O(total_fds). See the entry for \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR, above, for
… …
603.Sp 614.Sp
604This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and 615This backend maps \f(CW\*(C`EV_READ\*(C'\fR to \f(CW\*(C`POLLIN | POLLERR | POLLHUP\*(C'\fR, and
605\&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR. 616\&\f(CW\*(C`EV_WRITE\*(C'\fR to \f(CW\*(C`POLLOUT | POLLERR | POLLHUP\*(C'\fR.
606.ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4 617.ie n .IP """EVBACKEND_EPOLL"" (value 4, Linux)" 4
607.el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4 618.el .IP "\f(CWEVBACKEND_EPOLL\fR (value 4, Linux)" 4
608.IX Item "EVBACKEND_EPOLL (value 4, Linux)" 619.IX Item "EVBACKEND_EPOLL (value 4, Linux)"
609Use the linux-specific \fIepoll\fR\|(7) interface (for both pre\- and post\-2.6.9 620Use the linux-specific \fIepoll\fR\|(7) interface (for both pre\- and post\-2.6.9
610kernels). 621kernels).
611.Sp 622.Sp
612For few fds, this backend is a bit little slower than poll and select, but 623For few fds, this backend is a bit little slower than poll and select, but
613it scales phenomenally better. While poll and select usually scale like 624it scales phenomenally better. While poll and select usually scale like
… …
666.Sp 677.Sp
667This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as 678This backend maps \f(CW\*(C`EV_READ\*(C'\fR and \f(CW\*(C`EV_WRITE\*(C'\fR in the same way as
668\&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR. 679\&\f(CW\*(C`EVBACKEND_POLL\*(C'\fR.
669.ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4 680.ie n .IP """EVBACKEND_KQUEUE"" (value 8, most \s-1BSD\s0 clones)" 4
670.el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4 681.el .IP "\f(CWEVBACKEND_KQUEUE\fR (value 8, most \s-1BSD\s0 clones)" 4
671.IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)" 682.IX Item "EVBACKEND_KQUEUE (value 8, most BSD clones)"
672Kqueue deserves special mention, as at the time of this writing, it 683Kqueue deserves special mention, as at the time of this writing, it
673was broken on all BSDs except NetBSD (usually it doesn't work reliably 684was broken on all BSDs except NetBSD (usually it doesn't work reliably
674with anything but sockets and pipes, except on Darwin, where of course 685with anything but sockets and pipes, except on Darwin, where of course
675it's completely useless). Unlike epoll, however, whose brokenness 686it's completely useless). Unlike epoll, however, whose brokenness
676is by design, these kqueue bugs can (and eventually will) be fixed 687is by design, these kqueue bugs can (and eventually will) be fixed
… …
696While nominally embeddable in other event loops, this doesn't work 707While nominally embeddable in other event loops, this doesn't work
697everywhere, so you might need to test for this. And since it is broken 708everywhere, so you might need to test for this. And since it is broken
698almost everywhere, you should only use it when you have a lot of sockets 709almost everywhere, you should only use it when you have a lot of sockets
699(for which it usually works), by embedding it into another event loop 710(for which it usually works), by embedding it into another event loop
700(e.g. \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR (but \f(CW\*(C`poll\*(C'\fR is of course 711(e.g. \f(CW\*(C`EVBACKEND_SELECT\*(C'\fR or \f(CW\*(C`EVBACKEND_POLL\*(C'\fR (but \f(CW\*(C`poll\*(C'\fR is of course
701also broken on \s-1OS\s0 X)) and, did I mention it, using it only for sockets. 712also broken on \s-1OS X\s0)) and, did I mention it, using it only for sockets.
702.Sp 713.Sp
703This backend maps \f(CW\*(C`EV_READ\*(C'\fR into an \f(CW\*(C`EVFILT_READ\*(C'\fR kevent with 714This backend maps \f(CW\*(C`EV_READ\*(C'\fR into an \f(CW\*(C`EVFILT_READ\*(C'\fR kevent with
704\&\f(CW\*(C`NOTE_EOF\*(C'\fR, and \f(CW\*(C`EV_WRITE\*(C'\fR into an \f(CW\*(C`EVFILT_WRITE\*(C'\fR kevent with 715\&\f(CW\*(C`NOTE_EOF\*(C'\fR, and \f(CW\*(C`EV_WRITE\*(C'\fR into an \f(CW\*(C`EVFILT_WRITE\*(C'\fR kevent with
705\&\f(CW\*(C`NOTE_EOF\*(C'\fR. 716\&\f(CW\*(C`NOTE_EOF\*(C'\fR.
706.ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4 717.ie n .IP """EVBACKEND_DEVPOLL"" (value 16, Solaris 8)" 4
… …
710implementation). According to reports, \f(CW\*(C`/dev/poll\*(C'\fR only supports sockets 721implementation). According to reports, \f(CW\*(C`/dev/poll\*(C'\fR only supports sockets
711and is not embeddable, which would limit the usefulness of this backend 722and is not embeddable, which would limit the usefulness of this backend
712immensely. 723immensely.
713.ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4 724.ie n .IP """EVBACKEND_PORT"" (value 32, Solaris 10)" 4
714.el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4 725.el .IP "\f(CWEVBACKEND_PORT\fR (value 32, Solaris 10)" 4
715.IX Item "EVBACKEND_PORT (value 32, Solaris 10)" 726.IX Item "EVBACKEND_PORT (value 32, Solaris 10)"
716This uses the Solaris 10 event port mechanism. As with everything on Solaris, 727This uses the Solaris 10 event port mechanism. As with everything on Solaris,
717it's really slow, but it still scales very well (O(active_fds)). 728it's really slow, but it still scales very well (O(active_fds)).
718.Sp 729.Sp
719While this backend scales well, it requires one system call per active 730While this backend scales well, it requires one system call per active
720file descriptor per loop iteration. For small and medium numbers of file 731file descriptor per loop iteration. For small and medium numbers of file
… …
799except in the rare occasion where you really need to free its resources. 810except in the rare occasion where you really need to free its resources.
800If you need dynamically allocated loops it is better to use \f(CW\*(C`ev_loop_new\*(C'\fR 811If you need dynamically allocated loops it is better to use \f(CW\*(C`ev_loop_new\*(C'\fR
801and \f(CW\*(C`ev_loop_destroy\*(C'\fR. 812and \f(CW\*(C`ev_loop_destroy\*(C'\fR.
802.IP "ev_loop_fork (loop)" 4 813.IP "ev_loop_fork (loop)" 4
803.IX Item "ev_loop_fork (loop)" 814.IX Item "ev_loop_fork (loop)"
804This function sets a flag that causes subsequent \f(CW\*(C`ev_run\*(C'\fR iterations to 815This function sets a flag that causes subsequent \f(CW\*(C`ev_run\*(C'\fR iterations
805reinitialise the kernel state for backends that have one. Despite the 816to reinitialise the kernel state for backends that have one. Despite
806name, you can call it anytime, but it makes most sense after forking, in 817the name, you can call it anytime you are allowed to start or stop
807the child process. You \fImust\fR call it (or use \f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR) in the 818watchers (except inside an \f(CW\*(C`ev_prepare\*(C'\fR callback), but it makes most
808child before resuming or calling \f(CW\*(C`ev_run\*(C'\fR. 819sense after forking, in the child process. You \fImust\fR call it (or use
820\&\f(CW\*(C`EVFLAG_FORKCHECK\*(C'\fR) in the child before resuming or calling \f(CW\*(C`ev_run\*(C'\fR.
809.Sp 821.Sp
810Again, you \fIhave\fR to call it on \fIany\fR loop that you want to re-use after 822Again, you \fIhave\fR to call it on \fIany\fR loop that you want to re-use after
811a fork, \fIeven if you do not plan to use the loop in the parent\fR. This is 823a fork, \fIeven if you do not plan to use the loop in the parent\fR. This is
812because some kernel interfaces *cough* \fIkqueue\fR *cough* do funny things 824because some kernel interfaces *cough* \fIkqueue\fR *cough* do funny things
813during fork. 825during fork.
814.Sp 826.Sp
815On the other hand, you only need to call this function in the child 827On the other hand, you only need to call this function in the child
… …
1352example it might indicate that a fd is readable or writable, and if your 1364example it might indicate that a fd is readable or writable, and if your
1353callbacks is well-written it can just attempt the operation and cope with 1365callbacks is well-written it can just attempt the operation and cope with
1354the error from \fIread()\fR or \fIwrite()\fR. This will not work in multi-threaded 1366the error from \fIread()\fR or \fIwrite()\fR. This will not work in multi-threaded
1355programs, though, as the fd could already be closed and reused for another 1367programs, though, as the fd could already be closed and reused for another
1356thing, so beware. 1368thing, so beware.
1357.SS "\s-1GENERIC\s0 \s-1WATCHER\s0 \s-1FUNCTIONS\s0" 1369.SS "\s-1GENERIC WATCHER FUNCTIONS\s0"
1358.IX Subsection "GENERIC WATCHER FUNCTIONS" 1370.IX Subsection "GENERIC WATCHER FUNCTIONS"
1359.ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4 1371.ie n .IP """ev_init"" (ev_TYPE *watcher, callback)" 4
1360.el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4 1372.el .IP "\f(CWev_init\fR (ev_TYPE *watcher, callback)" 4
1361.IX Item "ev_init (ev_TYPE *watcher, callback)" 1373.IX Item "ev_init (ev_TYPE *watcher, callback)"
1362This macro initialises the generic portion of a watcher. The contents 1374This macro initialises the generic portion of a watcher. The contents
… …
1470or might not have been clamped to the valid range. 1482or might not have been clamped to the valid range.
1471.Sp 1483.Sp
1472The default priority used by watchers when no priority has been set is 1484The default priority used by watchers when no priority has been set is
1473always \f(CW0\fR, which is supposed to not be too high and not be too low :). 1485always \f(CW0\fR, which is supposed to not be too high and not be too low :).
1474.Sp 1486.Sp
1475See \*(L"\s-1WATCHER\s0 \s-1PRIORITY\s0 \s-1MODELS\s0\*(R", below, for a more thorough treatment of 1487See \*(L"\s-1WATCHER PRIORITY MODELS\*(R"\s0, below, for a more thorough treatment of
1476priorities. 1488priorities.
1477.IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4 1489.IP "ev_invoke (loop, ev_TYPE *watcher, int revents)" 4
1478.IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)" 1490.IX Item "ev_invoke (loop, ev_TYPE *watcher, int revents)"
1479Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither 1491Invoke the \f(CW\*(C`watcher\*(C'\fR with the given \f(CW\*(C`loop\*(C'\fR and \f(CW\*(C`revents\*(C'\fR. Neither
1480\&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback 1492\&\f(CW\*(C`loop\*(C'\fR nor \f(CW\*(C`revents\*(C'\fR need to be valid as long as the watcher callback
… …
1500not started in the first place. 1512not started in the first place.
1501.Sp 1513.Sp
1502See also \f(CW\*(C`ev_feed_fd_event\*(C'\fR and \f(CW\*(C`ev_feed_signal_event\*(C'\fR for related 1514See also \f(CW\*(C`ev_feed_fd_event\*(C'\fR and \f(CW\*(C`ev_feed_signal_event\*(C'\fR for related
1503functions that do not need a watcher. 1515functions that do not need a watcher.
1504.PP 1516.PP
1505See also the \*(L"\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0\*(R" and \*(L"\s-1BUILDING\s0 \s-1YOUR\s0 1517See also the \*(L"\s-1ASSOCIATING CUSTOM DATA WITH A WATCHER\*(R"\s0 and \*(L"\s-1BUILDING YOUR
1506\&\s-1OWN\s0 \s-1COMPOSITE\s0 \s-1WATCHERS\s0\*(R" idioms. 1518OWN COMPOSITE WATCHERS\*(R"\s0 idioms.
1507.SS "\s-1WATCHER\s0 \s-1STATES\s0" 1519.SS "\s-1WATCHER STATES\s0"
1508.IX Subsection "WATCHER STATES" 1520.IX Subsection "WATCHER STATES"
1509There are various watcher states mentioned throughout this manual \- 1521There are various watcher states mentioned throughout this manual \-
1510active, pending and so on. In this section these states and the rules to 1522active, pending and so on. In this section these states and the rules to
1511transition between them will be described in more detail \- and while these 1523transition between them will be described in more detail \- and while these
1512rules might look complicated, they usually do \*(L"the right thing\*(R". 1524rules might look complicated, they usually do \*(L"the right thing\*(R".
… …
1555.Sp 1567.Sp
1556While stopped (and not pending) the watcher is essentially in the 1568While stopped (and not pending) the watcher is essentially in the
1557initialised state, that is, it can be reused, moved, modified in any way 1569initialised state, that is, it can be reused, moved, modified in any way
1558you wish (but when you trash the memory block, you need to \f(CW\*(C`ev_TYPE_init\*(C'\fR 1570you wish (but when you trash the memory block, you need to \f(CW\*(C`ev_TYPE_init\*(C'\fR
1559it again). 1571it again).
1560.SS "\s-1WATCHER\s0 \s-1PRIORITY\s0 \s-1MODELS\s0" 1572.SS "\s-1WATCHER PRIORITY MODELS\s0"
1561.IX Subsection "WATCHER PRIORITY MODELS" 1573.IX Subsection "WATCHER PRIORITY MODELS"
1562Many event loops support \fIwatcher priorities\fR, which are usually small 1574Many event loops support \fIwatcher priorities\fR, which are usually small
1563integers that influence the ordering of event callback invocation 1575integers that influence the ordering of event callback invocation
1564between watchers in some way, all else being equal. 1576between watchers in some way, all else being equal.
1565.PP 1577.PP
… …
1763wish to read \- you would first have to request some data. 1775wish to read \- you would first have to request some data.
1764.PP 1776.PP
1765Since files are typically not-so-well supported by advanced notification 1777Since files are typically not-so-well supported by advanced notification
1766mechanism, libev tries hard to emulate \s-1POSIX\s0 behaviour with respect 1778mechanism, libev tries hard to emulate \s-1POSIX\s0 behaviour with respect
1767to files, even though you should not use it. The reason for this is 1779to files, even though you should not use it. The reason for this is
1768convenience: sometimes you want to watch \s-1STDIN\s0 or \s-1STDOUT\s0, which is 1780convenience: sometimes you want to watch \s-1STDIN\s0 or \s-1STDOUT,\s0 which is
1769usually a tty, often a pipe, but also sometimes files or special devices 1781usually a tty, often a pipe, but also sometimes files or special devices
1770(for example, \f(CW\*(C`epoll\*(C'\fR on Linux works with \fI/dev/random\fR but not with 1782(for example, \f(CW\*(C`epoll\*(C'\fR on Linux works with \fI/dev/random\fR but not with
1771\&\fI/dev/urandom\fR), and even though the file might better be served with 1783\&\fI/dev/urandom\fR), and even though the file might better be served with
1772asynchronous I/O instead of with non-blocking I/O, it is still useful when 1784asynchronous I/O instead of with non-blocking I/O, it is still useful when
1773it \*(L"just works\*(R" instead of freezing. 1785it \*(L"just works\*(R" instead of freezing.
1774.PP 1786.PP
1775So avoid file descriptors pointing to files when you know it (e.g. use 1787So avoid file descriptors pointing to files when you know it (e.g. use
1776libeio), but use them when it is convenient, e.g. for \s-1STDIN/STDOUT\s0, or 1788libeio), but use them when it is convenient, e.g. for \s-1STDIN/STDOUT,\s0 or
1777when you rarely read from a file instead of from a socket, and want to 1789when you rarely read from a file instead of from a socket, and want to
1778reuse the same code path. 1790reuse the same code path.
1779.PP 1791.PP
1780\fIThe special problem of fork\fR 1792\fIThe special problem of fork\fR
1781.IX Subsection "The special problem of fork" 1793.IX Subsection "The special problem of fork"
… …
1791\fIThe special problem of \s-1SIGPIPE\s0\fR 1803\fIThe special problem of \s-1SIGPIPE\s0\fR
1792.IX Subsection "The special problem of SIGPIPE" 1804.IX Subsection "The special problem of SIGPIPE"
1793.PP 1805.PP
1794While not really specific to libev, it is easy to forget about \f(CW\*(C`SIGPIPE\*(C'\fR: 1806While not really specific to libev, it is easy to forget about \f(CW\*(C`SIGPIPE\*(C'\fR:
1795when writing to a pipe whose other end has been closed, your program gets 1807when writing to a pipe whose other end has been closed, your program gets
1796sent a \s-1SIGPIPE\s0, which, by default, aborts your program. For most programs 1808sent a \s-1SIGPIPE,\s0 which, by default, aborts your program. For most programs
1797this is sensible behaviour, for daemons, this is usually undesirable. 1809this is sensible behaviour, for daemons, this is usually undesirable.
1798.PP 1810.PP
1799So when you encounter spurious, unexplained daemon exits, make sure you 1811So when you encounter spurious, unexplained daemon exits, make sure you
1800ignore \s-1SIGPIPE\s0 (and maybe make sure you log the exit status of your daemon 1812ignore \s-1SIGPIPE \s0(and maybe make sure you log the exit status of your daemon
1801somewhere, as that would have given you a big clue). 1813somewhere, as that would have given you a big clue).
1802.PP 1814.PP
1803\fIThe special problem of \fIaccept()\fIing when you can't\fR 1815\fIThe special problem of \fIaccept()\fIing when you can't\fR
1804.IX Subsection "The special problem of accept()ing when you can't" 1816.IX Subsection "The special problem of accept()ing when you can't"
1805.PP 1817.PP
1806Many implementations of the \s-1POSIX\s0 \f(CW\*(C`accept\*(C'\fR function (for example, 1818Many implementations of the \s-1POSIX \s0\f(CW\*(C`accept\*(C'\fR function (for example,
1807found in post\-2004 Linux) have the peculiar behaviour of not removing a 1819found in post\-2004 Linux) have the peculiar behaviour of not removing a
1808connection from the pending queue in all error cases. 1820connection from the pending queue in all error cases.
1809.PP 1821.PP
1810For example, larger servers often run out of file descriptors (because 1822For example, larger servers often run out of file descriptors (because
1811of resource limits), causing \f(CW\*(C`accept\*(C'\fR to fail with \f(CW\*(C`ENFILE\*(C'\fR but not 1823of resource limits), causing \f(CW\*(C`accept\*(C'\fR to fail with \f(CW\*(C`ENFILE\*(C'\fR but not
… …
2150.PP 2162.PP
2151The relative timeouts are calculated relative to the \f(CW\*(C`ev_now ()\*(C'\fR 2163The relative timeouts are calculated relative to the \f(CW\*(C`ev_now ()\*(C'\fR
2152time. This is usually the right thing as this timestamp refers to the time 2164time. This is usually the right thing as this timestamp refers to the time
2153of the event triggering whatever timeout you are modifying/starting. If 2165of the event triggering whatever timeout you are modifying/starting. If
2154you suspect event processing to be delayed and you \fIneed\fR to base the 2166you suspect event processing to be delayed and you \fIneed\fR to base the
2155timeout on the current time, use something like this to adjust for this: 2167timeout on the current time, use something like the following to adjust
2168for it:
2156.PP 2169.PP
2157.Vb 1 2170.Vb 1
2158\& ev_timer_set (&timer, after + ev_now () \- ev_time (), 0.); 2171\& ev_timer_set (&timer, after + (ev_time () \- ev_now ()), 0.);
2159.Ve 2172.Ve
2160.PP 2173.PP
2161If the event loop is suspended for a long time, you can also force an 2174If the event loop is suspended for a long time, you can also force an
2162update of the time returned by \f(CW\*(C`ev_now ()\*(C'\fR by calling \f(CW\*(C`ev_now_update 2175update of the time returned by \f(CW\*(C`ev_now ()\*(C'\fR by calling \f(CW\*(C`ev_now_update
2163()\*(C'\fR. 2176()\*(C'\fR, although that will push the event time of all outstanding events
2177further into the future.
2164.PP 2178.PP
2165\fIThe special problem of unsynchronised clocks\fR 2179\fIThe special problem of unsynchronised clocks\fR
2166.IX Subsection "The special problem of unsynchronised clocks" 2180.IX Subsection "The special problem of unsynchronised clocks"
2167.PP 2181.PP
2168Modern systems have a variety of clocks \- libev itself uses the normal 2182Modern systems have a variety of clocks \- libev itself uses the normal
… …
2416In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`offset\*(C'\fR are both being 2430In this mode the values for \f(CW\*(C`interval\*(C'\fR and \f(CW\*(C`offset\*(C'\fR are both being
2417ignored. Instead, each time the periodic watcher gets scheduled, the 2431ignored. Instead, each time the periodic watcher gets scheduled, the
2418reschedule callback will be called with the watcher as first, and the 2432reschedule callback will be called with the watcher as first, and the
2419current time as second argument. 2433current time as second argument.
2420.Sp 2434.Sp
2421\&\s-1NOTE:\s0 \fIThis callback \s-1MUST\s0 \s-1NOT\s0 stop or destroy any periodic watcher, ever, 2435\&\s-1NOTE: \s0\fIThis callback \s-1MUST NOT\s0 stop or destroy any periodic watcher, ever,
2422or make \s-1ANY\s0 other event loop modifications whatsoever, unless explicitly 2436or make \s-1ANY\s0 other event loop modifications whatsoever, unless explicitly
2423allowed by documentation here\fR. 2437allowed by documentation here\fR.
2424.Sp 2438.Sp
2425If you need to stop it, return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop 2439If you need to stop it, return \f(CW\*(C`now + 1e30\*(C'\fR (or so, fudge fudge) and stop
2426it afterwards (e.g. by starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is the 2440it afterwards (e.g. by starting an \f(CW\*(C`ev_prepare\*(C'\fR watcher, which is the
… …
2440It must return the next time to trigger, based on the passed time value 2454It must return the next time to trigger, based on the passed time value
2441(that is, the lowest time value larger than to the second argument). It 2455(that is, the lowest time value larger than to the second argument). It
2442will usually be called just before the callback will be triggered, but 2456will usually be called just before the callback will be triggered, but
2443might be called at other times, too. 2457might be called at other times, too.
2444.Sp 2458.Sp
2445\&\s-1NOTE:\s0 \fIThis callback must always return a time that is higher than or 2459\&\s-1NOTE: \s0\fIThis callback must always return a time that is higher than or
2446equal to the passed \f(CI\*(C`now\*(C'\fI value\fR. 2460equal to the passed \f(CI\*(C`now\*(C'\fI value\fR.
2447.Sp 2461.Sp
2448This can be used to create very complex timers, such as a timer that 2462This can be used to create very complex timers, such as a timer that
2449triggers on \*(L"next midnight, local time\*(R". To do this, you would calculate the 2463triggers on \*(L"next midnight, local time\*(R". To do this, you would calculate the
2450next midnight after \f(CW\*(C`now\*(C'\fR and return the timestamp value for this. How 2464next midnight after \f(CW\*(C`now\*(C'\fR and return the timestamp value for this. How
… …
2542only within the same loop, i.e. you can watch for \f(CW\*(C`SIGINT\*(C'\fR in your 2556only within the same loop, i.e. you can watch for \f(CW\*(C`SIGINT\*(C'\fR in your
2543default loop and for \f(CW\*(C`SIGIO\*(C'\fR in another loop, but you cannot watch for 2557default loop and for \f(CW\*(C`SIGIO\*(C'\fR in another loop, but you cannot watch for
2544\&\f(CW\*(C`SIGINT\*(C'\fR in both the default loop and another loop at the same time. At 2558\&\f(CW\*(C`SIGINT\*(C'\fR in both the default loop and another loop at the same time. At
2545the moment, \f(CW\*(C`SIGCHLD\*(C'\fR is permanently tied to the default loop. 2559the moment, \f(CW\*(C`SIGCHLD\*(C'\fR is permanently tied to the default loop.
2546.PP 2560.PP
2547When the first watcher gets started will libev actually register something 2561Only after the first watcher for a signal is started will libev actually
2548with the kernel (thus it coexists with your own signal handlers as long as 2562register something with the kernel. It thus coexists with your own signal
2549you don't register any with libev for the same signal). 2563handlers as long as you don't register any with libev for the same signal.
2550.PP 2564.PP
2551If possible and supported, libev will install its handlers with 2565If possible and supported, libev will install its handlers with
2552\&\f(CW\*(C`SA_RESTART\*(C'\fR (or equivalent) behaviour enabled, so system calls should 2566\&\f(CW\*(C`SA_RESTART\*(C'\fR (or equivalent) behaviour enabled, so system calls should
2553not be unduly interrupted. If you have a problem with system calls getting 2567not be unduly interrupted. If you have a problem with system calls getting
2554interrupted by signals you can block all signals in an \f(CW\*(C`ev_check\*(C'\fR watcher 2568interrupted by signals you can block all signals in an \f(CW\*(C`ev_check\*(C'\fR watcher
… …
2575The simplest way to ensure that the signal mask is reset in the child is 2589The simplest way to ensure that the signal mask is reset in the child is
2576to install a fork handler with \f(CW\*(C`pthread_atfork\*(C'\fR that resets it. That will 2590to install a fork handler with \f(CW\*(C`pthread_atfork\*(C'\fR that resets it. That will
2577catch fork calls done by libraries (such as the libc) as well. 2591catch fork calls done by libraries (such as the libc) as well.
2578.PP 2592.PP
2579In current versions of libev, the signal will not be blocked indefinitely 2593In current versions of libev, the signal will not be blocked indefinitely
2580unless you use the \f(CW\*(C`signalfd\*(C'\fR \s-1API\s0 (\f(CW\*(C`EV_SIGNALFD\*(C'\fR). While this reduces 2594unless you use the \f(CW\*(C`signalfd\*(C'\fR \s-1API \s0(\f(CW\*(C`EV_SIGNALFD\*(C'\fR). While this reduces
2581the window of opportunity for problems, it will not go away, as libev 2595the window of opportunity for problems, it will not go away, as libev
2582\&\fIhas\fR to modify the signal mask, at least temporarily. 2596\&\fIhas\fR to modify the signal mask, at least temporarily.
2583.PP 2597.PP
2584So I can't stress this enough: \fIIf you do not reset your signal mask when 2598So I can't stress this enough: \fIIf you do not reset your signal mask when
2585you expect it to be empty, you have a race condition in your code\fR. This 2599you expect it to be empty, you have a race condition in your code\fR. This
… …
2615The signal the watcher watches out for. 2629The signal the watcher watches out for.
2616.PP 2630.PP
2617\fIExamples\fR 2631\fIExamples\fR
2618.IX Subsection "Examples" 2632.IX Subsection "Examples"
2619.PP 2633.PP
2620Example: Try to exit cleanly on \s-1SIGINT\s0. 2634Example: Try to exit cleanly on \s-1SIGINT.\s0
2621.PP 2635.PP
2622.Vb 5 2636.Vb 5
2623\& static void 2637\& static void
2624\& sigint_cb (struct ev_loop *loop, ev_signal *w, int revents) 2638\& sigint_cb (struct ev_loop *loop, ev_signal *w, int revents)
2625\& { 2639\& {
… …
2782compilation environment, which means that on systems with large file 2796compilation environment, which means that on systems with large file
2783support disabled by default, you get the 32 bit version of the stat 2797support disabled by default, you get the 32 bit version of the stat
2784structure. When using the library from programs that change the \s-1ABI\s0 to 2798structure. When using the library from programs that change the \s-1ABI\s0 to
2785use 64 bit file offsets the programs will fail. In that case you have to 2799use 64 bit file offsets the programs will fail. In that case you have to
2786compile libev with the same flags to get binary compatibility. This is 2800compile libev with the same flags to get binary compatibility. This is
2787obviously the case with any flags that change the \s-1ABI\s0, but the problem is 2801obviously the case with any flags that change the \s-1ABI,\s0 but the problem is
2788most noticeably displayed with ev_stat and large file support. 2802most noticeably displayed with ev_stat and large file support.
2789.PP 2803.PP
2790The solution for this is to lobby your distribution maker to make large 2804The solution for this is to lobby your distribution maker to make large
2791file interfaces available by default (as e.g. FreeBSD does) and not 2805file interfaces available by default (as e.g. FreeBSD does) and not
2792optional. Libev cannot simply switch on large file support because it has 2806optional. Libev cannot simply switch on large file support because it has
… …
3037.IX Subsection "ev_prepare and ev_check - customise your event loop!" 3051.IX Subsection "ev_prepare and ev_check - customise your event loop!"
3038Prepare and check watchers are often (but not always) used in pairs: 3052Prepare and check watchers are often (but not always) used in pairs:
3039prepare watchers get invoked before the process blocks and check watchers 3053prepare watchers get invoked before the process blocks and check watchers
3040afterwards. 3054afterwards.
3041.PP 3055.PP
3042You \fImust not\fR call \f(CW\*(C`ev_run\*(C'\fR or similar functions that enter 3056You \fImust not\fR call \f(CW\*(C`ev_run\*(C'\fR (or similar functions that enter the
3043the current event loop from either \f(CW\*(C`ev_prepare\*(C'\fR or \f(CW\*(C`ev_check\*(C'\fR 3057current event loop) or \f(CW\*(C`ev_loop_fork\*(C'\fR from either \f(CW\*(C`ev_prepare\*(C'\fR or
3044watchers. Other loops than the current one are fine, however. The 3058\&\f(CW\*(C`ev_check\*(C'\fR watchers. Other loops than the current one are fine,
3045rationale behind this is that you do not need to check for recursion in 3059however. The rationale behind this is that you do not need to check
3046those watchers, i.e. the sequence will always be \f(CW\*(C`ev_prepare\*(C'\fR, blocking, 3060for recursion in those watchers, i.e. the sequence will always be
3047\&\f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each kind they will always be 3061\&\f(CW\*(C`ev_prepare\*(C'\fR, blocking, \f(CW\*(C`ev_check\*(C'\fR so if you have one watcher of each
3048called in pairs bracketing the blocking call. 3062kind they will always be called in pairs bracketing the blocking call.
3049.PP 3063.PP
3050Their main purpose is to integrate other event mechanisms into libev and 3064Their main purpose is to integrate other event mechanisms into libev and
3051their use is somewhat advanced. They could be used, for example, to track 3065their use is somewhat advanced. They could be used, for example, to track
3052variable changes, implement your own watchers, integrate net-snmp or a 3066variable changes, implement your own watchers, integrate net-snmp or a
3053coroutine library and lots more. They are also occasionally useful if 3067coroutine library and lots more. They are also occasionally useful if
… …
3223.Ve 3237.Ve
3224.PP 3238.PP
3225Method 4: Do not use a prepare or check watcher because the module you 3239Method 4: Do not use a prepare or check watcher because the module you
3226want to embed is not flexible enough to support it. Instead, you can 3240want to embed is not flexible enough to support it. Instead, you can
3227override their poll function. The drawback with this solution is that the 3241override their poll function. The drawback with this solution is that the
3228main loop is now no longer controllable by \s-1EV\s0. The \f(CW\*(C`Glib::EV\*(C'\fR module uses 3242main loop is now no longer controllable by \s-1EV.\s0 The \f(CW\*(C`Glib::EV\*(C'\fR module uses
3229this approach, effectively embedding \s-1EV\s0 as a client into the horrible 3243this approach, effectively embedding \s-1EV\s0 as a client into the horrible
3230libglib event loop. 3244libglib event loop.
3231.PP 3245.PP
3232.Vb 4 3246.Vb 4
3233\& static gint 3247\& static gint
… …
3347.PP 3361.PP
3348.Vb 3 3362.Vb 3
3349\& struct ev_loop *loop_hi = ev_default_init (0); 3363\& struct ev_loop *loop_hi = ev_default_init (0);
3350\& struct ev_loop *loop_lo = 0; 3364\& struct ev_loop *loop_lo = 0;
3351\& ev_embed embed; 3365\& ev_embed embed;
3352\& 3366\&
3353\& // see if there is a chance of getting one that works 3367\& // see if there is a chance of getting one that works
3354\& // (remember that a flags value of 0 means autodetection) 3368\& // (remember that a flags value of 0 means autodetection)
3355\& loop_lo = ev_embeddable_backends () & ev_recommended_backends () 3369\& loop_lo = ev_embeddable_backends () & ev_recommended_backends ()
3356\& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ()) 3370\& ? ev_loop_new (ev_embeddable_backends () & ev_recommended_backends ())
3357\& : 0; 3371\& : 0;
… …
3373.PP 3387.PP
3374.Vb 3 3388.Vb 3
3375\& struct ev_loop *loop = ev_default_init (0); 3389\& struct ev_loop *loop = ev_default_init (0);
3376\& struct ev_loop *loop_socket = 0; 3390\& struct ev_loop *loop_socket = 0;
3377\& ev_embed embed; 3391\& ev_embed embed;
3378\& 3392\&
3379\& if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE) 3393\& if (ev_supported_backends () & ~ev_recommended_backends () & EVBACKEND_KQUEUE)
3380\& if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE)) 3394\& if ((loop_socket = ev_loop_new (EVBACKEND_KQUEUE))
3381\& { 3395\& {
3382\& ev_embed_init (&embed, 0, loop_socket); 3396\& ev_embed_init (&embed, 0, loop_socket);
3383\& ev_embed_start (loop, &embed); 3397\& ev_embed_start (loop, &embed);
… …
3400of course. 3414of course.
3401.PP 3415.PP
3402\fIThe special problem of life after fork \- how is it possible?\fR 3416\fIThe special problem of life after fork \- how is it possible?\fR
3403.IX Subsection "The special problem of life after fork - how is it possible?" 3417.IX Subsection "The special problem of life after fork - how is it possible?"
3404.PP 3418.PP
3405Most uses of \f(CW\*(C`fork()\*(C'\fR consist of forking, then some simple calls to set 3419Most uses of \f(CW\*(C`fork ()\*(C'\fR consist of forking, then some simple calls to set
3406up/change the process environment, followed by a call to \f(CW\*(C`exec()\*(C'\fR. This 3420up/change the process environment, followed by a call to \f(CW\*(C`exec()\*(C'\fR. This
3407sequence should be handled by libev without any problems. 3421sequence should be handled by libev without any problems.
3408.PP 3422.PP
3409This changes when the application actually wants to do event handling 3423This changes when the application actually wants to do event handling
3410in the child, or both parent in child, in effect \*(L"continuing\*(R" after the 3424in the child, or both parent in child, in effect \*(L"continuing\*(R" after the
… …
3650\&\f(CW\*(C`EV_ERROR\*(C'\fR, \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or \f(CW\*(C`EV_TIMER\*(C'\fR) and the \f(CW\*(C`arg\*(C'\fR 3664\&\f(CW\*(C`EV_ERROR\*(C'\fR, \f(CW\*(C`EV_READ\*(C'\fR, \f(CW\*(C`EV_WRITE\*(C'\fR or \f(CW\*(C`EV_TIMER\*(C'\fR) and the \f(CW\*(C`arg\*(C'\fR
3651value passed to \f(CW\*(C`ev_once\*(C'\fR. Note that it is possible to receive \fIboth\fR 3665value passed to \f(CW\*(C`ev_once\*(C'\fR. Note that it is possible to receive \fIboth\fR
3652a timeout and an io event at the same time \- you probably should give io 3666a timeout and an io event at the same time \- you probably should give io
3653events precedence. 3667events precedence.
3654.Sp 3668.Sp
3655Example: wait up to ten seconds for data to appear on \s-1STDIN_FILENO\s0. 3669Example: wait up to ten seconds for data to appear on \s-1STDIN_FILENO.\s0
3656.Sp 3670.Sp
3657.Vb 7 3671.Vb 7
3658\& static void stdin_ready (int revents, void *arg) 3672\& static void stdin_ready (int revents, void *arg)
3659\& { 3673\& {
3660\& if (revents & EV_READ) 3674\& if (revents & EV_READ)
… …
3676.SH "COMMON OR USEFUL IDIOMS (OR BOTH)" 3690.SH "COMMON OR USEFUL IDIOMS (OR BOTH)"
3677.IX Header "COMMON OR USEFUL IDIOMS (OR BOTH)" 3691.IX Header "COMMON OR USEFUL IDIOMS (OR BOTH)"
3678This section explains some common idioms that are not immediately 3692This section explains some common idioms that are not immediately
3679obvious. Note that examples are sprinkled over the whole manual, and this 3693obvious. Note that examples are sprinkled over the whole manual, and this
3680section only contains stuff that wouldn't fit anywhere else. 3694section only contains stuff that wouldn't fit anywhere else.
3681.SS "\s-1ASSOCIATING\s0 \s-1CUSTOM\s0 \s-1DATA\s0 \s-1WITH\s0 A \s-1WATCHER\s0" 3695.SS "\s-1ASSOCIATING CUSTOM DATA WITH A WATCHER\s0"
3682.IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER" 3696.IX Subsection "ASSOCIATING CUSTOM DATA WITH A WATCHER"
3683Each watcher has, by default, a \f(CW\*(C`void *data\*(C'\fR member that you can read 3697Each watcher has, by default, a \f(CW\*(C`void *data\*(C'\fR member that you can read
3684or modify at any time: libev will completely ignore it. This can be used 3698or modify at any time: libev will completely ignore it. This can be used
3685to associate arbitrary data with your watcher. If you need more data and 3699to associate arbitrary data with your watcher. If you need more data and
3686don't want to allocate memory separately and store a pointer to it in that 3700don't want to allocate memory separately and store a pointer to it in that
… …
3712\& } 3726\& }
3713.Ve 3727.Ve
3714.PP 3728.PP
3715More interesting and less C\-conformant ways of casting your callback 3729More interesting and less C\-conformant ways of casting your callback
3716function type instead have been omitted. 3730function type instead have been omitted.
3717.SS "\s-1BUILDING\s0 \s-1YOUR\s0 \s-1OWN\s0 \s-1COMPOSITE\s0 \s-1WATCHERS\s0" 3731.SS "\s-1BUILDING YOUR OWN COMPOSITE WATCHERS\s0"
3718.IX Subsection "BUILDING YOUR OWN COMPOSITE WATCHERS" 3732.IX Subsection "BUILDING YOUR OWN COMPOSITE WATCHERS"
3719Another common scenario is to use some data structure with multiple 3733Another common scenario is to use some data structure with multiple
3720embedded watchers, in effect creating your own watcher that combines 3734embedded watchers, in effect creating your own watcher that combines
3721multiple libev event sources into one \*(L"super-watcher\*(R": 3735multiple libev event sources into one \*(L"super-watcher\*(R":
3722.PP 3736.PP
… …
3750\& { 3764\& {
3751\& struct my_biggy big = (struct my_biggy *) 3765\& struct my_biggy big = (struct my_biggy *)
3752\& (((char *)w) \- offsetof (struct my_biggy, t2)); 3766\& (((char *)w) \- offsetof (struct my_biggy, t2));
3753\& } 3767\& }
3754.Ve 3768.Ve
3755.SS "\s-1AVOIDING\s0 \s-1FINISHING\s0 \s-1BEFORE\s0 \s-1RETURNING\s0" 3769.SS "\s-1AVOIDING FINISHING BEFORE RETURNING\s0"
3756.IX Subsection "AVOIDING FINISHING BEFORE RETURNING" 3770.IX Subsection "AVOIDING FINISHING BEFORE RETURNING"
3757Often you have structures like this in event-based programs: 3771Often you have structures like this in event-based programs:
3758.PP 3772.PP
3759.Vb 4 3773.Vb 4
3760\& callback () 3774\& callback ()
… …
3793\& ev_feed_event (EV_A_ watcher, 0); 3807\& ev_feed_event (EV_A_ watcher, 0);
3794.Ve 3808.Ve
3795.PP 3809.PP
3796This way, \f(CW\*(C`start_new_request\*(C'\fR can safely return before the callback is 3810This way, \f(CW\*(C`start_new_request\*(C'\fR can safely return before the callback is
3797invoked, while not delaying callback invocation too much. 3811invoked, while not delaying callback invocation too much.
3798.SS "\s-1MODEL/NESTED\s0 \s-1EVENT\s0 \s-1LOOP\s0 \s-1INVOCATIONS\s0 \s-1AND\s0 \s-1EXIT\s0 \s-1CONDITIONS\s0" 3812.SS "\s-1MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS\s0"
3799.IX Subsection "MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS" 3813.IX Subsection "MODEL/NESTED EVENT LOOP INVOCATIONS AND EXIT CONDITIONS"
3800Often (especially in \s-1GUI\s0 toolkits) there are places where you have 3814Often (especially in \s-1GUI\s0 toolkits) there are places where you have
3801\&\fImodal\fR interaction, which is most easily implemented by recursively 3815\&\fImodal\fR interaction, which is most easily implemented by recursively
3802invoking \f(CW\*(C`ev_run\*(C'\fR. 3816invoking \f(CW\*(C`ev_run\*(C'\fR.
3803.PP 3817.PP
… …
3835\& exit_main_loop = 1; 3849\& exit_main_loop = 1;
3836\& 3850\&
3837\& // exit both 3851\& // exit both
3838\& exit_main_loop = exit_nested_loop = 1; 3852\& exit_main_loop = exit_nested_loop = 1;
3839.Ve 3853.Ve
3840.SS "\s-1THREAD\s0 \s-1LOCKING\s0 \s-1EXAMPLE\s0" 3854.SS "\s-1THREAD LOCKING EXAMPLE\s0"
3841.IX Subsection "THREAD LOCKING EXAMPLE" 3855.IX Subsection "THREAD LOCKING EXAMPLE"
3842Here is a fictitious example of how to run an event loop in a different 3856Here is a fictitious example of how to run an event loop in a different
3843thread from where callbacks are being invoked and watchers are 3857thread from where callbacks are being invoked and watchers are
3844created/added/removed. 3858created/added/removed.
3845.PP 3859.PP
… …
3986.PP 4000.PP
3987Note that sending the \f(CW\*(C`ev_async\*(C'\fR watcher is required because otherwise 4001Note that sending the \f(CW\*(C`ev_async\*(C'\fR watcher is required because otherwise
3988an event loop currently blocking in the kernel will have no knowledge 4002an event loop currently blocking in the kernel will have no knowledge
3989about the newly added timer. By waking up the loop it will pick up any new 4003about the newly added timer. By waking up the loop it will pick up any new
3990watchers in the next event loop iteration. 4004watchers in the next event loop iteration.
3991.SS "\s-1THREADS\s0, \s-1COROUTINES\s0, \s-1CONTINUATIONS\s0, \s-1QUEUES\s0... \s-1INSTEAD\s0 \s-1OF\s0 \s-1CALLBACKS\s0" 4005.SS "\s-1THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS\s0"
3992.IX Subsection "THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS" 4006.IX Subsection "THREADS, COROUTINES, CONTINUATIONS, QUEUES... INSTEAD OF CALLBACKS"
3993While the overhead of a callback that e.g. schedules a thread is small, it 4007While the overhead of a callback that e.g. schedules a thread is small, it
3994is still an overhead. If you embed libev, and your main usage is with some 4008is still an overhead. If you embed libev, and your main usage is with some
3995kind of threads or coroutines, you might want to customise libev so that 4009kind of threads or coroutines, you might want to customise libev so that
3996doesn't need callbacks anymore. 4010doesn't need callbacks anymore.
… …
4032You can do similar tricks if you have, say, threads with an event queue \- 4046You can do similar tricks if you have, say, threads with an event queue \-
4033instead of storing a coroutine, you store the queue object and instead of 4047instead of storing a coroutine, you store the queue object and instead of
4034switching to a coroutine, you push the watcher onto the queue and notify 4048switching to a coroutine, you push the watcher onto the queue and notify
4035any waiters. 4049any waiters.
4036.PP 4050.PP
4037To embed libev, see \*(L"\s-1EMBEDDING\s0\*(R", but in short, it's easiest to create two 4051To embed libev, see \*(L"\s-1EMBEDDING\*(R"\s0, but in short, it's easiest to create two
4038files, \fImy_ev.h\fR and \fImy_ev.c\fR that include the respective libev files: 4052files, \fImy_ev.h\fR and \fImy_ev.c\fR that include the respective libev files:
4039.PP 4053.PP
4040.Vb 4 4054.Vb 4
4041\& // my_ev.h 4055\& // my_ev.h
4042\& #define EV_CB_DECLARE(type) struct my_coro *cb; 4056\& #define EV_CB_DECLARE(type) struct my_coro *cb;
4043\& #define EV_CB_INVOKE(watcher) switch_to ((watcher)\->cb); 4057\& #define EV_CB_INVOKE(watcher) switch_to ((watcher)\->cb)
4044\& #include "../libev/ev.h" 4058\& #include "../libev/ev.h"
4045\& 4059\&
4046\& // my_ev.c 4060\& // my_ev.c
4047\& #define EV_H "my_ev.h" 4061\& #define EV_H "my_ev.h"
4048\& #include "../libev/ev.c" 4062\& #include "../libev/ev.c"
… …
4234\& void operator() (ev::io &w, int revents) 4248\& void operator() (ev::io &w, int revents)
4235\& { 4249\& {
4236\& ... 4250\& ...
4237\& } 4251\& }
4238\& } 4252\& }
4239\& 4253\&
4240\& myfunctor f; 4254\& myfunctor f;
4241\& 4255\&
4242\& ev::io w; 4256\& ev::io w;
4243\& w.set (&f); 4257\& w.set (&f);
4244.Ve 4258.Ve
… …
4337there are additional modules that implement libev-compatible interfaces 4351there are additional modules that implement libev-compatible interfaces
4338to \f(CW\*(C`libadns\*(C'\fR (\f(CW\*(C`EV::ADNS\*(C'\fR, but \f(CW\*(C`AnyEvent::DNS\*(C'\fR is preferred nowadays), 4352to \f(CW\*(C`libadns\*(C'\fR (\f(CW\*(C`EV::ADNS\*(C'\fR, but \f(CW\*(C`AnyEvent::DNS\*(C'\fR is preferred nowadays),
4339\&\f(CW\*(C`Net::SNMP\*(C'\fR (\f(CW\*(C`Net::SNMP::EV\*(C'\fR) and the \f(CW\*(C`libglib\*(C'\fR event core (\f(CW\*(C`Glib::EV\*(C'\fR 4353\&\f(CW\*(C`Net::SNMP\*(C'\fR (\f(CW\*(C`Net::SNMP::EV\*(C'\fR) and the \f(CW\*(C`libglib\*(C'\fR event core (\f(CW\*(C`Glib::EV\*(C'\fR
4340and \f(CW\*(C`EV::Glib\*(C'\fR). 4354and \f(CW\*(C`EV::Glib\*(C'\fR).
4341.Sp 4355.Sp
4342It can be found and installed via \s-1CPAN\s0, its homepage is at 4356It can be found and installed via \s-1CPAN,\s0 its homepage is at
4343<http://software.schmorp.de/pkg/EV>. 4357<http://software.schmorp.de/pkg/EV>.
4344.IP "Python" 4 4358.IP "Python" 4
4345.IX Item "Python" 4359.IX Item "Python"
4346Python bindings can be found at <http://code.google.com/p/pyev/>. It 4360Python bindings can be found at <http://code.google.com/p/pyev/>. It
4347seems to be quite complete and well-documented. 4361seems to be quite complete and well-documented.
… …
4355Roger Pack reports that using the link order \f(CW\*(C`\-lws2_32 \-lmsvcrt\-ruby\-190\*(C'\fR 4369Roger Pack reports that using the link order \f(CW\*(C`\-lws2_32 \-lmsvcrt\-ruby\-190\*(C'\fR
4356makes rev work even on mingw. 4370makes rev work even on mingw.
4357.IP "Haskell" 4 4371.IP "Haskell" 4
4358.IX Item "Haskell" 4372.IX Item "Haskell"
4359A haskell binding to libev is available at 4373A haskell binding to libev is available at
4360http://hackage.haskell.org/cgi\-bin/hackage\-scripts/package/hlibev <http://hackage.haskell.org/cgi-bin/hackage-scripts/package/hlibev>. 4374<http://hackage.haskell.org/cgi\-bin/hackage\-scripts/package/hlibev>.
4361.IP "D" 4 4375.IP "D" 4
4362.IX Item "D" 4376.IX Item "D"
4363Leandro Lucarella has written a D language binding (\fIev.d\fR) for libev, to 4377Leandro Lucarella has written a D language binding (\fIev.d\fR) for libev, to
4364be found at <http://www.llucax.com.ar/proj/ev.d/index.html>. 4378be found at <http://www.llucax.com.ar/proj/ev.d/index.html>.
4365.IP "Ocaml" 4 4379.IP "Ocaml" 4
4366.IX Item "Ocaml" 4380.IX Item "Ocaml"
4367Erkki Seppala has written Ocaml bindings for libev, to be found at 4381Erkki Seppala has written Ocaml bindings for libev, to be found at
4368http://modeemi.cs.tut.fi/~flux/software/ocaml\-ev/ <http://modeemi.cs.tut.fi/~flux/software/ocaml-ev/>. 4382<http://modeemi.cs.tut.fi/~flux/software/ocaml\-ev/>.
4369.IP "Lua" 4 4383.IP "Lua" 4
4370.IX Item "Lua" 4384.IX Item "Lua"
4371Brian Maher has written a partial interface to libev for lua (at the 4385Brian Maher has written a partial interface to libev for lua (at the
4372time of this writing, only \f(CW\*(C`ev_io\*(C'\fR and \f(CW\*(C`ev_timer\*(C'\fR), to be found at 4386time of this writing, only \f(CW\*(C`ev_io\*(C'\fR and \f(CW\*(C`ev_timer\*(C'\fR), to be found at
4373http://github.com/brimworks/lua\-ev <http://github.com/brimworks/lua-ev>. 4387<http://github.com/brimworks/lua\-ev>.
4374.IP "Javascript" 4 4388.IP "Javascript" 4
4375.IX Item "Javascript" 4389.IX Item "Javascript"
4376Node.js (<http://nodejs.org>) uses libev as the underlying event library. 4390Node.js (<http://nodejs.org>) uses libev as the underlying event library.
4377.IP "Others" 4 4391.IP "Others" 4
4378.IX Item "Others" 4392.IX Item "Others"
… …
4467.SS "\s-1FILESETS\s0" 4481.SS "\s-1FILESETS\s0"
4468.IX Subsection "FILESETS" 4482.IX Subsection "FILESETS"
4469Depending on what features you need you need to include one or more sets of files 4483Depending on what features you need you need to include one or more sets of files
4470in your application. 4484in your application.
4471.PP 4485.PP
4472\fI\s-1CORE\s0 \s-1EVENT\s0 \s-1LOOP\s0\fR 4486\fI\s-1CORE EVENT LOOP\s0\fR
4473.IX Subsection "CORE EVENT LOOP" 4487.IX Subsection "CORE EVENT LOOP"
4474.PP 4488.PP
4475To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual 4489To include only the libev core (all the \f(CW\*(C`ev_*\*(C'\fR functions), with manual
4476configuration (no autoconf): 4490configuration (no autoconf):
4477.PP 4491.PP
… …
4480\& #include "ev.c" 4494\& #include "ev.c"
4481.Ve 4495.Ve
4482.PP 4496.PP
4483This will automatically include \fIev.h\fR, too, and should be done in a 4497This will automatically include \fIev.h\fR, too, and should be done in a
4484single C source file only to provide the function implementations. To use 4498single C source file only to provide the function implementations. To use
4485it, do the same for \fIev.h\fR in all files wishing to use this \s-1API\s0 (best 4499it, do the same for \fIev.h\fR in all files wishing to use this \s-1API \s0(best
4486done by writing a wrapper around \fIev.h\fR that you can include instead and 4500done by writing a wrapper around \fIev.h\fR that you can include instead and
4487where you can put other configuration options): 4501where you can put other configuration options):
4488.PP 4502.PP
4489.Vb 2 4503.Vb 2
4490\& #define EV_STANDALONE 1 4504\& #define EV_STANDALONE 1
… …
4514.Ve 4528.Ve
4515.PP 4529.PP
4516\&\fIev.c\fR includes the backend files directly when enabled, so you only need 4530\&\fIev.c\fR includes the backend files directly when enabled, so you only need
4517to compile this single file. 4531to compile this single file.
4518.PP 4532.PP
4519\fI\s-1LIBEVENT\s0 \s-1COMPATIBILITY\s0 \s-1API\s0\fR 4533\fI\s-1LIBEVENT COMPATIBILITY API\s0\fR
4520.IX Subsection "LIBEVENT COMPATIBILITY API" 4534.IX Subsection "LIBEVENT COMPATIBILITY API"
4521.PP 4535.PP
4522To include the libevent compatibility \s-1API\s0, also include: 4536To include the libevent compatibility \s-1API,\s0 also include:
4523.PP 4537.PP
4524.Vb 1 4538.Vb 1
4525\& #include "event.c" 4539\& #include "event.c"
4526.Ve 4540.Ve
4527.PP 4541.PP
… …
4529.PP 4543.PP
4530.Vb 1 4544.Vb 1
4531\& #include "event.h" 4545\& #include "event.h"
4532.Ve 4546.Ve
4533.PP 4547.PP
4534in the files that want to use the libevent \s-1API\s0. This also includes \fIev.h\fR. 4548in the files that want to use the libevent \s-1API.\s0 This also includes \fIev.h\fR.
4535.PP 4549.PP
4536You need the following additional files for this: 4550You need the following additional files for this:
4537.PP 4551.PP
4538.Vb 2 4552.Vb 2
4539\& event.h 4553\& event.h
4540\& event.c 4554\& event.c
4541.Ve 4555.Ve
4542.PP 4556.PP
4543\fI\s-1AUTOCONF\s0 \s-1SUPPORT\s0\fR 4557\fI\s-1AUTOCONF SUPPORT\s0\fR
4544.IX Subsection "AUTOCONF SUPPORT" 4558.IX Subsection "AUTOCONF SUPPORT"
4545.PP 4559.PP
4546Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your configuration in 4560Instead of using \f(CW\*(C`EV_STANDALONE=1\*(C'\fR and providing your configuration in
4547whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your 4561whatever way you want, you can also \f(CW\*(C`m4_include([libev.m4])\*(C'\fR in your
4548\&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then 4562\&\fIconfigure.ac\fR and leave \f(CW\*(C`EV_STANDALONE\*(C'\fR undefined. \fIev.c\fR will then
… …
4551For this of course you need the m4 file: 4565For this of course you need the m4 file:
4552.PP 4566.PP
4553.Vb 1 4567.Vb 1
4554\& libev.m4 4568\& libev.m4
4555.Ve 4569.Ve
4556.SS "\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0" 4570.SS "\s-1PREPROCESSOR SYMBOLS/MACROS\s0"
4557.IX Subsection "PREPROCESSOR SYMBOLS/MACROS" 4571.IX Subsection "PREPROCESSOR SYMBOLS/MACROS"
4558Libev can be configured via a variety of preprocessor symbols you have to 4572Libev can be configured via a variety of preprocessor symbols you have to
4559define before including (or compiling) any of its files. The default in 4573define before including (or compiling) any of its files. The default in
4560the absence of autoconf is documented for every option. 4574the absence of autoconf is documented for every option.
4561.PP 4575.PP
4562Symbols marked with \*(L"(h)\*(R" do not change the \s-1ABI\s0, and can have different 4576Symbols marked with \*(L"(h)\*(R" do not change the \s-1ABI,\s0 and can have different
4563values when compiling libev vs. including \fIev.h\fR, so it is permissible 4577values when compiling libev vs. including \fIev.h\fR, so it is permissible
4564to redefine them before including \fIev.h\fR without breaking compatibility 4578to redefine them before including \fIev.h\fR without breaking compatibility
4565to a compiled library. All other symbols change the \s-1ABI\s0, which means all 4579to a compiled library. All other symbols change the \s-1ABI,\s0 which means all
4566users of libev and the libev code itself must be compiled with compatible 4580users of libev and the libev code itself must be compiled with compatible
4567settings. 4581settings.
4568.IP "\s-1EV_COMPAT3\s0 (h)" 4 4582.IP "\s-1EV_COMPAT3 \s0(h)" 4
4569.IX Item "EV_COMPAT3 (h)" 4583.IX Item "EV_COMPAT3 (h)"
4570Backwards compatibility is a major concern for libev. This is why this 4584Backwards compatibility is a major concern for libev. This is why this
4571release of libev comes with wrappers for the functions and symbols that 4585release of libev comes with wrappers for the functions and symbols that
4572have been renamed between libev version 3 and 4. 4586have been renamed between libev version 3 and 4.
4573.Sp 4587.Sp
… …
4578typedef in that case. 4592typedef in that case.
4579.Sp 4593.Sp
4580In some future version, the default for \f(CW\*(C`EV_COMPAT3\*(C'\fR will become \f(CW0\fR, 4594In some future version, the default for \f(CW\*(C`EV_COMPAT3\*(C'\fR will become \f(CW0\fR,
4581and in some even more future version the compatibility code will be 4595and in some even more future version the compatibility code will be
4582removed completely. 4596removed completely.
4583.IP "\s-1EV_STANDALONE\s0 (h)" 4 4597.IP "\s-1EV_STANDALONE \s0(h)" 4
4584.IX Item "EV_STANDALONE (h)" 4598.IX Item "EV_STANDALONE (h)"
4585Must always be \f(CW1\fR if you do not use autoconf configuration, which 4599Must always be \f(CW1\fR if you do not use autoconf configuration, which
4586keeps libev from including \fIconfig.h\fR, and it also defines dummy 4600keeps libev from including \fIconfig.h\fR, and it also defines dummy
4587implementations for some libevent functions (such as logging, which is not 4601implementations for some libevent functions (such as logging, which is not
4588supported). It will also not define any of the structs usually found in 4602supported). It will also not define any of the structs usually found in
… …
4746handler \*(L"locking\*(R" as well as for signal and thread safety in \f(CW\*(C`ev_async\*(C'\fR 4760handler \*(L"locking\*(R" as well as for signal and thread safety in \f(CW\*(C`ev_async\*(C'\fR
4747watchers. 4761watchers.
4748.Sp 4762.Sp
4749In the absence of this define, libev will use \f(CW\*(C`sig_atomic_t volatile\*(C'\fR 4763In the absence of this define, libev will use \f(CW\*(C`sig_atomic_t volatile\*(C'\fR
4750(from \fIsignal.h\fR), which is usually good enough on most platforms. 4764(from \fIsignal.h\fR), which is usually good enough on most platforms.
4751.IP "\s-1EV_H\s0 (h)" 4 4765.IP "\s-1EV_H \s0(h)" 4
4752.IX Item "EV_H (h)" 4766.IX Item "EV_H (h)"
4753The name of the \fIev.h\fR header file used to include it. The default if 4767The name of the \fIev.h\fR header file used to include it. The default if
4754undefined is \f(CW"ev.h"\fR in \fIevent.h\fR, \fIev.c\fR and \fIev++.h\fR. This can be 4768undefined is \f(CW"ev.h"\fR in \fIevent.h\fR, \fIev.c\fR and \fIev++.h\fR. This can be
4755used to virtually rename the \fIev.h\fR header file in case of conflicts. 4769used to virtually rename the \fIev.h\fR header file in case of conflicts.
4756.IP "\s-1EV_CONFIG_H\s0 (h)" 4 4770.IP "\s-1EV_CONFIG_H \s0(h)" 4
4757.IX Item "EV_CONFIG_H (h)" 4771.IX Item "EV_CONFIG_H (h)"
4758If \f(CW\*(C`EV_STANDALONE\*(C'\fR isn't \f(CW1\fR, this variable can be used to override 4772If \f(CW\*(C`EV_STANDALONE\*(C'\fR isn't \f(CW1\fR, this variable can be used to override
4759\&\fIev.c\fR's idea of where to find the \fIconfig.h\fR file, similarly to 4773\&\fIev.c\fR's idea of where to find the \fIconfig.h\fR file, similarly to
4760\&\f(CW\*(C`EV_H\*(C'\fR, above. 4774\&\f(CW\*(C`EV_H\*(C'\fR, above.
4761.IP "\s-1EV_EVENT_H\s0 (h)" 4 4775.IP "\s-1EV_EVENT_H \s0(h)" 4
4762.IX Item "EV_EVENT_H (h)" 4776.IX Item "EV_EVENT_H (h)"
4763Similarly to \f(CW\*(C`EV_H\*(C'\fR, this macro can be used to override \fIevent.c\fR's idea 4777Similarly to \f(CW\*(C`EV_H\*(C'\fR, this macro can be used to override \fIevent.c\fR's idea
4764of how the \fIevent.h\fR header can be found, the default is \f(CW"event.h"\fR. 4778of how the \fIevent.h\fR header can be found, the default is \f(CW"event.h"\fR.
4765.IP "\s-1EV_PROTOTYPES\s0 (h)" 4 4779.IP "\s-1EV_PROTOTYPES \s0(h)" 4
4766.IX Item "EV_PROTOTYPES (h)" 4780.IX Item "EV_PROTOTYPES (h)"
4767If defined to be \f(CW0\fR, then \fIev.h\fR will not define any function 4781If defined to be \f(CW0\fR, then \fIev.h\fR will not define any function
4768prototypes, but still define all the structs and other symbols. This is 4782prototypes, but still define all the structs and other symbols. This is
4769occasionally useful if you want to provide your own wrapper functions 4783occasionally useful if you want to provide your own wrapper functions
4770around libev functions. 4784around libev functions.
… …
4794all the priorities, so having many of them (hundreds) uses a lot of space 4808all the priorities, so having many of them (hundreds) uses a lot of space
4795and time, so using the defaults of five priorities (\-2 .. +2) is usually 4809and time, so using the defaults of five priorities (\-2 .. +2) is usually
4796fine. 4810fine.
4797.Sp 4811.Sp
4798If your embedding application does not need any priorities, defining these 4812If your embedding application does not need any priorities, defining these
4799both to \f(CW0\fR will save some memory and \s-1CPU\s0. 4813both to \f(CW0\fR will save some memory and \s-1CPU.\s0
4800.IP "\s-1EV_PERIODIC_ENABLE\s0, \s-1EV_IDLE_ENABLE\s0, \s-1EV_EMBED_ENABLE\s0, \s-1EV_STAT_ENABLE\s0, \s-1EV_PREPARE_ENABLE\s0, \s-1EV_CHECK_ENABLE\s0, \s-1EV_FORK_ENABLE\s0, \s-1EV_SIGNAL_ENABLE\s0, \s-1EV_ASYNC_ENABLE\s0, \s-1EV_CHILD_ENABLE\s0." 4 4814.IP "\s-1EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE.\s0" 4
4801.IX Item "EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE." 4815.IX Item "EV_PERIODIC_ENABLE, EV_IDLE_ENABLE, EV_EMBED_ENABLE, EV_STAT_ENABLE, EV_PREPARE_ENABLE, EV_CHECK_ENABLE, EV_FORK_ENABLE, EV_SIGNAL_ENABLE, EV_ASYNC_ENABLE, EV_CHILD_ENABLE."
4802If undefined or defined to be \f(CW1\fR (and the platform supports it), then 4816If undefined or defined to be \f(CW1\fR (and the platform supports it), then
4803the respective watcher type is supported. If defined to be \f(CW0\fR, then it 4817the respective watcher type is supported. If defined to be \f(CW0\fR, then it
4804is not. Disabling watcher types mainly saves code size. 4818is not. Disabling watcher types mainly saves code size.
4805.IP "\s-1EV_FEATURES\s0" 4 4819.IP "\s-1EV_FEATURES\s0" 4
… …
4979.Vb 3 4993.Vb 3
4980\& #define EV_COMMON \e 4994\& #define EV_COMMON \e
4981\& SV *self; /* contains this struct */ \e 4995\& SV *self; /* contains this struct */ \e
4982\& SV *cb_sv, *fh /* note no trailing ";" */ 4996\& SV *cb_sv, *fh /* note no trailing ";" */
4983.Ve 4997.Ve
4984.IP "\s-1EV_CB_DECLARE\s0 (type)" 4 4998.IP "\s-1EV_CB_DECLARE \s0(type)" 4
4985.IX Item "EV_CB_DECLARE (type)" 4999.IX Item "EV_CB_DECLARE (type)"
4986.PD 0 5000.PD 0
4987.IP "\s-1EV_CB_INVOKE\s0 (watcher, revents)" 4 5001.IP "\s-1EV_CB_INVOKE \s0(watcher, revents)" 4
4988.IX Item "EV_CB_INVOKE (watcher, revents)" 5002.IX Item "EV_CB_INVOKE (watcher, revents)"
4989.IP "ev_set_cb (ev, cb)" 4 5003.IP "ev_set_cb (ev, cb)" 4
4990.IX Item "ev_set_cb (ev, cb)" 5004.IX Item "ev_set_cb (ev, cb)"
4991.PD 5005.PD
4992Can be used to change the callback member declaration in each watcher, 5006Can be used to change the callback member declaration in each watcher,
4993and the way callbacks are invoked and set. Must expand to a struct member 5007and the way callbacks are invoked and set. Must expand to a struct member
4994definition and a statement, respectively. See the \fIev.h\fR header file for 5008definition and a statement, respectively. See the \fIev.h\fR header file for
4995their default definitions. One possible use for overriding these is to 5009their default definitions. One possible use for overriding these is to
4996avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use 5010avoid the \f(CW\*(C`struct ev_loop *\*(C'\fR as first argument in all cases, or to use
4997method calls instead of plain function calls in \*(C+. 5011method calls instead of plain function calls in \*(C+.
4998.SS "\s-1EXPORTED\s0 \s-1API\s0 \s-1SYMBOLS\s0" 5012.SS "\s-1EXPORTED API SYMBOLS\s0"
4999.IX Subsection "EXPORTED API SYMBOLS" 5013.IX Subsection "EXPORTED API SYMBOLS"
5000If you need to re-export the \s-1API\s0 (e.g. via a \s-1DLL\s0) and you need a list of 5014If you need to re-export the \s-1API \s0(e.g. via a \s-1DLL\s0) and you need a list of
5001exported symbols, you can use the provided \fISymbol.*\fR files which list 5015exported symbols, you can use the provided \fISymbol.*\fR files which list
5002all public symbols, one per line: 5016all public symbols, one per line:
5003.PP 5017.PP
5004.Vb 2 5018.Vb 2
5005\& Symbols.ev for libev proper 5019\& Symbols.ev for libev proper
… …
5057\& #include "ev_cpp.h" 5071\& #include "ev_cpp.h"
5058\& #include "ev.c" 5072\& #include "ev.c"
5059.Ve 5073.Ve
5060.SH "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" 5074.SH "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT"
5061.IX Header "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT" 5075.IX Header "INTERACTION WITH OTHER PROGRAMS, LIBRARIES OR THE ENVIRONMENT"
5062.SS "\s-1THREADS\s0 \s-1AND\s0 \s-1COROUTINES\s0" 5076.SS "\s-1THREADS AND COROUTINES\s0"
5063.IX Subsection "THREADS AND COROUTINES" 5077.IX Subsection "THREADS AND COROUTINES"
5064\fI\s-1THREADS\s0\fR 5078\fI\s-1THREADS\s0\fR
5065.IX Subsection "THREADS" 5079.IX Subsection "THREADS"
5066.PP 5080.PP
5067All libev functions are reentrant and thread-safe unless explicitly 5081All libev functions are reentrant and thread-safe unless explicitly
… …
5113An example use would be to communicate signals or other events that only 5127An example use would be to communicate signals or other events that only
5114work in the default loop by registering the signal watcher with the 5128work in the default loop by registering the signal watcher with the
5115default loop and triggering an \f(CW\*(C`ev_async\*(C'\fR watcher from the default loop 5129default loop and triggering an \f(CW\*(C`ev_async\*(C'\fR watcher from the default loop
5116watcher callback into the event loop interested in the signal. 5130watcher callback into the event loop interested in the signal.
5117.PP 5131.PP
5118See also \*(L"\s-1THREAD\s0 \s-1LOCKING\s0 \s-1EXAMPLE\s0\*(R". 5132See also \*(L"\s-1THREAD LOCKING EXAMPLE\*(R"\s0.
5119.PP 5133.PP
5120\fI\s-1COROUTINES\s0\fR 5134\fI\s-1COROUTINES\s0\fR
5121.IX Subsection "COROUTINES" 5135.IX Subsection "COROUTINES"
5122.PP 5136.PP
5123Libev is very accommodating to coroutines (\*(L"cooperative threads\*(R"): 5137Libev is very accommodating to coroutines (\*(L"cooperative threads\*(R"):
… …
5128that you must not do this from \f(CW\*(C`ev_periodic\*(C'\fR reschedule callbacks. 5142that you must not do this from \f(CW\*(C`ev_periodic\*(C'\fR reschedule callbacks.
5129.PP 5143.PP
5130Care has been taken to ensure that libev does not keep local state inside 5144Care has been taken to ensure that libev does not keep local state inside
5131\&\f(CW\*(C`ev_run\*(C'\fR, and other calls do not usually allow for coroutine switches as 5145\&\f(CW\*(C`ev_run\*(C'\fR, and other calls do not usually allow for coroutine switches as
5132they do not call any callbacks. 5146they do not call any callbacks.
5133.SS "\s-1COMPILER\s0 \s-1WARNINGS\s0" 5147.SS "\s-1COMPILER WARNINGS\s0"
5134.IX Subsection "COMPILER WARNINGS" 5148.IX Subsection "COMPILER WARNINGS"
5135Depending on your compiler and compiler settings, you might get no or a 5149Depending on your compiler and compiler settings, you might get no or a
5136lot of warnings when compiling libev code. Some people are apparently 5150lot of warnings when compiling libev code. Some people are apparently
5137scared by this. 5151scared by this.
5138.PP 5152.PP
… …
5190.PP 5204.PP
5191If you need, for some reason, empty reports from valgrind for your project 5205If you need, for some reason, empty reports from valgrind for your project
5192I suggest using suppression lists. 5206I suggest using suppression lists.
5193.SH "PORTABILITY NOTES" 5207.SH "PORTABILITY NOTES"
5194.IX Header "PORTABILITY NOTES" 5208.IX Header "PORTABILITY NOTES"
5195.SS "\s-1GNU/LINUX\s0 32 \s-1BIT\s0 \s-1LIMITATIONS\s0" 5209.SS "\s-1GNU/LINUX 32 BIT LIMITATIONS\s0"
5196.IX Subsection "GNU/LINUX 32 BIT LIMITATIONS" 5210.IX Subsection "GNU/LINUX 32 BIT LIMITATIONS"
5197GNU/Linux is the only common platform that supports 64 bit file/large file 5211GNU/Linux is the only common platform that supports 64 bit file/large file
5198interfaces but \fIdisables\fR them by default. 5212interfaces but \fIdisables\fR them by default.
5199.PP 5213.PP
5200That means that libev compiled in the default environment doesn't support 5214That means that libev compiled in the default environment doesn't support
5201files larger than 2GiB or so, which mainly affects \f(CW\*(C`ev_stat\*(C'\fR watchers. 5215files larger than 2GiB or so, which mainly affects \f(CW\*(C`ev_stat\*(C'\fR watchers.
5202.PP 5216.PP
5203Unfortunately, many programs try to work around this GNU/Linux issue 5217Unfortunately, many programs try to work around this GNU/Linux issue
5204by enabling the large file \s-1API\s0, which makes them incompatible with the 5218by enabling the large file \s-1API,\s0 which makes them incompatible with the
5205standard libev compiled for their system. 5219standard libev compiled for their system.
5206.PP 5220.PP
5207Likewise, libev cannot enable the large file \s-1API\s0 itself as this would 5221Likewise, libev cannot enable the large file \s-1API\s0 itself as this would
5208suddenly make it incompatible to the default compile time environment, 5222suddenly make it incompatible to the default compile time environment,
5209i.e. all programs not using special compile switches. 5223i.e. all programs not using special compile switches.
5210.SS "\s-1OS/X\s0 \s-1AND\s0 \s-1DARWIN\s0 \s-1BUGS\s0" 5224.SS "\s-1OS/X AND DARWIN BUGS\s0"
5211.IX Subsection "OS/X AND DARWIN BUGS" 5225.IX Subsection "OS/X AND DARWIN BUGS"
5212The whole thing is a bug if you ask me \- basically any system interface 5226The whole thing is a bug if you ask me \- basically any system interface
5213you touch is broken, whether it is locales, poll, kqueue or even the 5227you touch is broken, whether it is locales, poll, kqueue or even the
5214OpenGL drivers. 5228OpenGL drivers.
5215.PP 5229.PP
… …
5237.PP 5251.PP
5238\fI\f(CI\*(C`select\*(C'\fI is buggy\fR 5252\fI\f(CI\*(C`select\*(C'\fI is buggy\fR
5239.IX Subsection "select is buggy" 5253.IX Subsection "select is buggy"
5240.PP 5254.PP
5241All that's left is \f(CW\*(C`select\*(C'\fR, and of course Apple found a way to fuck this 5255All that's left is \f(CW\*(C`select\*(C'\fR, and of course Apple found a way to fuck this
5242one up as well: On \s-1OS/X\s0, \f(CW\*(C`select\*(C'\fR actively limits the number of file 5256one up as well: On \s-1OS/X, \s0\f(CW\*(C`select\*(C'\fR actively limits the number of file
5243descriptors you can pass in to 1024 \- your program suddenly crashes when 5257descriptors you can pass in to 1024 \- your program suddenly crashes when
5244you use more. 5258you use more.
5245.PP 5259.PP
5246There is an undocumented \*(L"workaround\*(R" for this \- defining 5260There is an undocumented \*(L"workaround\*(R" for this \- defining
5247\&\f(CW\*(C`_DARWIN_UNLIMITED_SELECT\*(C'\fR, which libev tries to use, so select \fIshould\fR 5261\&\f(CW\*(C`_DARWIN_UNLIMITED_SELECT\*(C'\fR, which libev tries to use, so select \fIshould\fR
5248work on \s-1OS/X\s0. 5262work on \s-1OS/X.\s0
5249.SS "\s-1SOLARIS\s0 \s-1PROBLEMS\s0 \s-1AND\s0 \s-1WORKAROUNDS\s0" 5263.SS "\s-1SOLARIS PROBLEMS AND WORKAROUNDS\s0"
5250.IX Subsection "SOLARIS PROBLEMS AND WORKAROUNDS" 5264.IX Subsection "SOLARIS PROBLEMS AND WORKAROUNDS"
5251\fI\f(CI\*(C`errno\*(C'\fI reentrancy\fR 5265\fI\f(CI\*(C`errno\*(C'\fI reentrancy\fR
5252.IX Subsection "errno reentrancy" 5266.IX Subsection "errno reentrancy"
5253.PP 5267.PP
5254The default compile environment on Solaris is unfortunately so 5268The default compile environment on Solaris is unfortunately so
… …
5271great. 5285great.
5272.PP 5286.PP
5273If you can't get it to work, you can try running the program by setting 5287If you can't get it to work, you can try running the program by setting
5274the environment variable \f(CW\*(C`LIBEV_FLAGS=3\*(C'\fR to only allow \f(CW\*(C`poll\*(C'\fR and 5288the environment variable \f(CW\*(C`LIBEV_FLAGS=3\*(C'\fR to only allow \f(CW\*(C`poll\*(C'\fR and
5275\&\f(CW\*(C`select\*(C'\fR backends. 5289\&\f(CW\*(C`select\*(C'\fR backends.
5276.SS "\s-1AIX\s0 \s-1POLL\s0 \s-1BUG\s0" 5290.SS "\s-1AIX POLL BUG\s0"
5277.IX Subsection "AIX POLL BUG" 5291.IX Subsection "AIX POLL BUG"
5278\&\s-1AIX\s0 unfortunately has a broken \f(CW\*(C`poll.h\*(C'\fR header. Libev works around 5292\&\s-1AIX\s0 unfortunately has a broken \f(CW\*(C`poll.h\*(C'\fR header. Libev works around
5279this by trying to avoid the poll backend altogether (i.e. it's not even 5293this by trying to avoid the poll backend altogether (i.e. it's not even
5280compiled in), which normally isn't a big problem as \f(CW\*(C`select\*(C'\fR works fine 5294compiled in), which normally isn't a big problem as \f(CW\*(C`select\*(C'\fR works fine
5281with large bitsets on \s-1AIX\s0, and \s-1AIX\s0 is dead anyway. 5295with large bitsets on \s-1AIX,\s0 and \s-1AIX\s0 is dead anyway.
5282.SS "\s-1WIN32\s0 \s-1PLATFORM\s0 \s-1LIMITATIONS\s0 \s-1AND\s0 \s-1WORKAROUNDS\s0" 5296.SS "\s-1WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS\s0"
5283.IX Subsection "WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS" 5297.IX Subsection "WIN32 PLATFORM LIMITATIONS AND WORKAROUNDS"
5284\fIGeneral issues\fR 5298\fIGeneral issues\fR
5285.IX Subsection "General issues" 5299.IX Subsection "General issues"
5286.PP 5300.PP
5287Win32 doesn't support any of the standards (e.g. \s-1POSIX\s0) that libev 5301Win32 doesn't support any of the standards (e.g. \s-1POSIX\s0) that libev
… …
5356\& #define EV_USE_SELECT 1 5370\& #define EV_USE_SELECT 1
5357\& #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */ 5371\& #define EV_SELECT_IS_WINSOCKET 1 /* forces EV_SELECT_USE_FD_SET, too */
5358.Ve 5372.Ve
5359.PP 5373.PP
5360Note that winsockets handling of fd sets is O(n), so you can easily get a 5374Note that winsockets handling of fd sets is O(n), so you can easily get a
5361complexity in the O(nA\*^X) range when using win32. 5375complexity in the O(nX) range when using win32.
5362.PP 5376.PP
5363\fILimited number of file descriptors\fR 5377\fILimited number of file descriptors\fR
5364.IX Subsection "Limited number of file descriptors" 5378.IX Subsection "Limited number of file descriptors"
5365.PP 5379.PP
5366Windows has numerous arbitrary (and low) limits on things. 5380Windows has numerous arbitrary (and low) limits on things.
… …
5382by calling \f(CW\*(C`_setmaxstdio\*(C'\fR, which can increase this limit to \f(CW2048\fR 5396by calling \f(CW\*(C`_setmaxstdio\*(C'\fR, which can increase this limit to \f(CW2048\fR
5383(another arbitrary limit), but is broken in many versions of the Microsoft 5397(another arbitrary limit), but is broken in many versions of the Microsoft
5384runtime libraries. This might get you to about \f(CW512\fR or \f(CW2048\fR sockets 5398runtime libraries. This might get you to about \f(CW512\fR or \f(CW2048\fR sockets
5385(depending on windows version and/or the phase of the moon). To get more, 5399(depending on windows version and/or the phase of the moon). To get more,
5386you need to wrap all I/O functions and provide your own fd management, but 5400you need to wrap all I/O functions and provide your own fd management, but
5387the cost of calling select (O(nA\*^X)) will likely make this unworkable. 5401the cost of calling select (O(nX)) will likely make this unworkable.
5388.SS "\s-1PORTABILITY\s0 \s-1REQUIREMENTS\s0" 5402.SS "\s-1PORTABILITY REQUIREMENTS\s0"
5389.IX Subsection "PORTABILITY REQUIREMENTS" 5403.IX Subsection "PORTABILITY REQUIREMENTS"
5390In addition to a working ISO-C implementation and of course the 5404In addition to a working ISO-C implementation and of course the
5391backend-specific APIs, libev relies on a few additional extensions: 5405backend-specific APIs, libev relies on a few additional extensions:
5392.ie n .IP """void (*)(ev_watcher_type *, int revents)"" must have compatible calling conventions regardless of ""ev_watcher_type *""." 4 5406.ie n .IP """void (*)(ev_watcher_type *, int revents)"" must have compatible calling conventions regardless of ""ev_watcher_type *""." 4
5393.el .IP "\f(CWvoid (*)(ev_watcher_type *, int revents)\fR must have compatible calling conventions regardless of \f(CWev_watcher_type *\fR." 4 5407.el .IP "\f(CWvoid (*)(ev_watcher_type *, int revents)\fR must have compatible calling conventions regardless of \f(CWev_watcher_type *\fR." 4
5394.IX Item "void (*)(ev_watcher_type *, int revents) must have compatible calling conventions regardless of ev_watcher_type *." 5408.IX Item "void (*)(ev_watcher_type *, int revents) must have compatible calling conventions regardless of ev_watcher_type *."
5395Libev assumes not only that all watcher pointers have the same internal 5409Libev assumes not only that all watcher pointers have the same internal
5396structure (guaranteed by \s-1POSIX\s0 but not by \s-1ISO\s0 C for example), but it also 5410structure (guaranteed by \s-1POSIX\s0 but not by \s-1ISO C\s0 for example), but it also
5397assumes that the same (machine) code can be used to call any watcher 5411assumes that the same (machine) code can be used to call any watcher
5398callback: The watcher callbacks have different type signatures, but libev 5412callback: The watcher callbacks have different type signatures, but libev
5399calls them using an \f(CW\*(C`ev_watcher *\*(C'\fR internally. 5413calls them using an \f(CW\*(C`ev_watcher *\*(C'\fR internally.
5400.IP "pointer accesses must be thread-atomic" 4 5414.IP "pointer accesses must be thread-atomic" 4
5401.IX Item "pointer accesses must be thread-atomic" 5415.IX Item "pointer accesses must be thread-atomic"
… …
5422except the initial one, and run the signal handling loop in the initial 5436except the initial one, and run the signal handling loop in the initial
5423thread as well. 5437thread as well.
5424.ie n .IP """long"" must be large enough for common memory allocation sizes" 4 5438.ie n .IP """long"" must be large enough for common memory allocation sizes" 4
5425.el .IP "\f(CWlong\fR must be large enough for common memory allocation sizes" 4 5439.el .IP "\f(CWlong\fR must be large enough for common memory allocation sizes" 4
5426.IX Item "long must be large enough for common memory allocation sizes" 5440.IX Item "long must be large enough for common memory allocation sizes"
5427To improve portability and simplify its \s-1API\s0, libev uses \f(CW\*(C`long\*(C'\fR internally 5441To improve portability and simplify its \s-1API,\s0 libev uses \f(CW\*(C`long\*(C'\fR internally
5428instead of \f(CW\*(C`size_t\*(C'\fR when allocating its data structures. On non-POSIX 5442instead of \f(CW\*(C`size_t\*(C'\fR when allocating its data structures. On non-POSIX
5429systems (Microsoft...) this might be unexpectedly low, but is still at 5443systems (Microsoft...) this might be unexpectedly low, but is still at
5430least 31 bits everywhere, which is enough for hundreds of millions of 5444least 31 bits everywhere, which is enough for hundreds of millions of
5431watchers. 5445watchers.
5432.ie n .IP """double"" must hold a time value in seconds with enough accuracy" 4 5446.ie n .IP """double"" must hold a time value in seconds with enough accuracy" 4
… …
5434.IX Item "double must hold a time value in seconds with enough accuracy" 5448.IX Item "double must hold a time value in seconds with enough accuracy"
5435The type \f(CW\*(C`double\*(C'\fR is used to represent timestamps. It is required to 5449The type \f(CW\*(C`double\*(C'\fR is used to represent timestamps. It is required to
5436have at least 51 bits of mantissa (and 9 bits of exponent), which is 5450have at least 51 bits of mantissa (and 9 bits of exponent), which is
5437good enough for at least into the year 4000 with millisecond accuracy 5451good enough for at least into the year 4000 with millisecond accuracy
5438(the design goal for libev). This requirement is overfulfilled by 5452(the design goal for libev). This requirement is overfulfilled by
5439implementations using \s-1IEEE\s0 754, which is basically all existing ones. 5453implementations using \s-1IEEE 754,\s0 which is basically all existing ones.
5440.Sp 5454.Sp
5441With \s-1IEEE\s0 754 doubles, you get microsecond accuracy until at least the 5455With \s-1IEEE 754\s0 doubles, you get microsecond accuracy until at least the
5442year 2255 (and millisecond accuracy till the year 287396 \- by then, libev 5456year 2255 (and millisecond accuracy till the year 287396 \- by then, libev
5443is either obsolete or somebody patched it to use \f(CW\*(C`long double\*(C'\fR or 5457is either obsolete or somebody patched it to use \f(CW\*(C`long double\*(C'\fR or
5444something like that, just kidding). 5458something like that, just kidding).
5445.PP 5459.PP
5446If you know of other additional requirements drop me a note. 5460If you know of other additional requirements drop me a note.
… …
5508calls in the current loop iteration and the loop is currently 5522calls in the current loop iteration and the loop is currently
5509blocked. Checking for async and signal events involves iterating over all 5523blocked. Checking for async and signal events involves iterating over all
5510running async watchers or all signal numbers. 5524running async watchers or all signal numbers.
5511.SH "PORTING FROM LIBEV 3.X TO 4.X" 5525.SH "PORTING FROM LIBEV 3.X TO 4.X"
5512.IX Header "PORTING FROM LIBEV 3.X TO 4.X" 5526.IX Header "PORTING FROM LIBEV 3.X TO 4.X"
5513The major version 4 introduced some incompatible changes to the \s-1API\s0. 5527The major version 4 introduced some incompatible changes to the \s-1API.\s0
5514.PP 5528.PP
5515At the moment, the \f(CW\*(C`ev.h\*(C'\fR header file provides compatibility definitions 5529At the moment, the \f(CW\*(C`ev.h\*(C'\fR header file provides compatibility definitions
5516for all changes, so most programs should still compile. The compatibility 5530for all changes, so most programs should still compile. The compatibility
5517layer might be removed in later versions of libev, so better update to the 5531layer might be removed in later versions of libev, so better update to the
5518new \s-1API\s0 early than late. 5532new \s-1API\s0 early than late.
5519.ie n .IP """EV_COMPAT3"" backwards compatibility mechanism" 4 5533.ie n .IP """EV_COMPAT3"" backwards compatibility mechanism" 4
5520.el .IP "\f(CWEV_COMPAT3\fR backwards compatibility mechanism" 4 5534.el .IP "\f(CWEV_COMPAT3\fR backwards compatibility mechanism" 4
5521.IX Item "EV_COMPAT3 backwards compatibility mechanism" 5535.IX Item "EV_COMPAT3 backwards compatibility mechanism"
5522The backward compatibility mechanism can be controlled by 5536The backward compatibility mechanism can be controlled by
5523\&\f(CW\*(C`EV_COMPAT3\*(C'\fR. See \*(L"\s-1PREPROCESSOR\s0 \s-1SYMBOLS/MACROS\s0\*(R" in the \*(L"\s-1EMBEDDING\s0\*(R" 5537\&\f(CW\*(C`EV_COMPAT3\*(C'\fR. See \*(L"\s-1PREPROCESSOR SYMBOLS/MACROS\*(R"\s0 in the \*(L"\s-1EMBEDDING\*(R"\s0
5524section. 5538section.
5525.ie n .IP """ev_default_destroy"" and ""ev_default_fork"" have been removed" 4 5539.ie n .IP """ev_default_destroy"" and ""ev_default_fork"" have been removed" 4
5526.el .IP "\f(CWev_default_destroy\fR and \f(CWev_default_fork\fR have been removed" 4 5540.el .IP "\f(CWev_default_destroy\fR and \f(CWev_default_fork\fR have been removed" 4
5527.IX Item "ev_default_destroy and ev_default_fork have been removed" 5541.IX Item "ev_default_destroy and ev_default_fork have been removed"
5528These calls can be replaced easily by their \f(CW\*(C`ev_loop_xxx\*(C'\fR counterparts: 5542These calls can be replaced easily by their \f(CW\*(C`ev_loop_xxx\*(C'\fR counterparts:
… …
5568.SH "GLOSSARY" 5582.SH "GLOSSARY"
5569.IX Header "GLOSSARY" 5583.IX Header "GLOSSARY"
5570.IP "active" 4 5584.IP "active" 4
5571.IX Item "active" 5585.IX Item "active"
5572A watcher is active as long as it has been started and not yet stopped. 5586A watcher is active as long as it has been started and not yet stopped.
5573See \*(L"\s-1WATCHER\s0 \s-1STATES\s0\*(R" for details. 5587See \*(L"\s-1WATCHER STATES\*(R"\s0 for details.
5574.IP "application" 4 5588.IP "application" 4
5575.IX Item "application" 5589.IX Item "application"
5576In this document, an application is whatever is using libev. 5590In this document, an application is whatever is using libev.
5577.IP "backend" 4 5591.IP "backend" 4
5578.IX Item "backend" 5592.IX Item "backend"
… …
5605The model used to describe how an event loop handles and processes 5619The model used to describe how an event loop handles and processes
5606watchers and events. 5620watchers and events.
5607.IP "pending" 4 5621.IP "pending" 4
5608.IX Item "pending" 5622.IX Item "pending"
5609A watcher is pending as soon as the corresponding event has been 5623A watcher is pending as soon as the corresponding event has been
5610detected. See \*(L"\s-1WATCHER\s0 \s-1STATES\s0\*(R" for details. 5624detected. See \*(L"\s-1WATCHER STATES\*(R"\s0 for details.
5611.IP "real time" 4 5625.IP "real time" 4
5612.IX Item "real time" 5626.IX Item "real time"
5613The physical time that is observed. It is apparently strictly monotonic :) 5627The physical time that is observed. It is apparently strictly monotonic :)
5614.IP "wall-clock time" 4 5628.IP "wall-clock time" 4
5615.IX Item "wall-clock time" 5629.IX Item "wall-clock time"

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines