[ViewVC] Diff of: cvs/libev/ev.pod

Comparing libev/ev.pod (file contents):
Revision 1.1 by root, Mon Nov 12 07:58:13 2007 UTC vs.
Revision 1.31 by root, Fri Nov 23 05:00:45 2007 UTC

…		…
8		8
9	=head1 DESCRIPTION	9	=head1 DESCRIPTION
10		10
11	Libev is an event loop: you register interest in certain events (such as a	11	Libev is an event loop: you register interest in certain events (such as a
12	file descriptor being readable or a timeout occuring), and it will manage	12	file descriptor being readable or a timeout occuring), and it will manage
13	these event sources and provide your program events.	13	these event sources and provide your program with events.
14		14
15	To do this, it must take more or less complete control over your process	15	To do this, it must take more or less complete control over your process
16	(or thread) by executing the I<event loop> handler, and will then	16	(or thread) by executing the I<event loop> handler, and will then
17	communicate events via a callback mechanism.	17	communicate events via a callback mechanism.
18		18
…		…
25		25
26	Libev supports select, poll, the linux-specific epoll and the bsd-specific	26	Libev supports select, poll, the linux-specific epoll and the bsd-specific
27	kqueue mechanisms for file descriptor events, relative timers, absolute	27	kqueue mechanisms for file descriptor events, relative timers, absolute
28	timers with customised rescheduling, signal events, process status change	28	timers with customised rescheduling, signal events, process status change
29	events (related to SIGCHLD), and event watchers dealing with the event	29	events (related to SIGCHLD), and event watchers dealing with the event
30	loop mechanism itself (idle, prepare and check watchers).	30	loop mechanism itself (idle, prepare and check watchers). It also is quite
		31	fast (see this L<benchmark\|http://libev.schmorp.de/bench.html> comparing
		32	it to libevent for example).
31		33
32	=head1 CONVENTIONS	34	=head1 CONVENTIONS
33		35
34	Libev is very configurable. In this manual the default configuration	36	Libev is very configurable. In this manual the default configuration
35	will be described, which supports multiple event loops. For more info	37	will be described, which supports multiple event loops. For more info
36	about various configuraiton options please have a look at the file	38	about various configuration options please have a look at the file
37	F<README.embed> in the libev distribution. If libev was configured without	39	F<README.embed> in the libev distribution. If libev was configured without
38	support for multiple event loops, then all functions taking an initial	40	support for multiple event loops, then all functions taking an initial
39	argument of name C<loop> (which is always of type C<struct ev_loop *>)	41	argument of name C<loop> (which is always of type C<struct ev_loop *>)
40	will not have this argument.	42	will not have this argument.
41		43
42	=head1 TIME AND OTHER GLOBAL FUNCTIONS	44	=head1 TIME REPRESENTATION
43		45
44	Libev represents time as a single floating point number. This type is	46	Libev represents time as a single floating point number, representing the
		47	(fractional) number of seconds since the (POSIX) epoch (somewhere near
		48	the beginning of 1970, details are complicated, don't ask). This type is
45	called C<ev_tstamp>, which is what you should use too. It usually aliases	49	called C<ev_tstamp>, which is what you should use too. It usually aliases
46	to the double type in C.	50	to the double type in C.
47		51
		52	=head1 GLOBAL FUNCTIONS
		53
		54	These functions can be called anytime, even before initialising the
		55	library in any way.
		56
48	=over 4	57	=over 4
49		58
50	=item ev_tstamp ev_time ()	59	=item ev_tstamp ev_time ()
51		60
52	Returns the current time as libev would use it.	61	Returns the current time as libev would use it. Please note that the
		62	C<ev_now> function is usually faster and also often returns the timestamp
		63	you actually want to know.
53		64
54	=item int ev_version_major ()	65	=item int ev_version_major ()
55		66
56	=item int ev_version_minor ()	67	=item int ev_version_minor ()
57		68
…		…
59	you linked against by calling the functions C<ev_version_major> and	70	you linked against by calling the functions C<ev_version_major> and
60	C<ev_version_minor>. If you want, you can compare against the global	71	C<ev_version_minor>. If you want, you can compare against the global
61	symbols C<EV_VERSION_MAJOR> and C<EV_VERSION_MINOR>, which specify the	72	symbols C<EV_VERSION_MAJOR> and C<EV_VERSION_MINOR>, which specify the
62	version of the library your program was compiled against.	73	version of the library your program was compiled against.
63		74
64	Usually, its a good idea to terminate if the major versions mismatch,	75	Usually, it's a good idea to terminate if the major versions mismatch,
65	as this indicates an incompatible change. Minor versions are usually	76	as this indicates an incompatible change. Minor versions are usually
66	compatible to older versions, so a larger minor version alone is usually	77	compatible to older versions, so a larger minor version alone is usually
67	not a problem.	78	not a problem.
68		79
		80	=item unsigned int ev_supported_backends ()
		81
		82	Return the set of all backends (i.e. their corresponding C<EV_BACKEND_*>
		83	value) compiled into this binary of libev (independent of their
		84	availability on the system you are running on). See C<ev_default_loop> for
		85	a description of the set values.
		86
		87	=item unsigned int ev_recommended_backends ()
		88
		89	Return the set of all backends compiled into this binary of libev and also
		90	recommended for this platform. This set is often smaller than the one
		91	returned by C<ev_supported_backends>, as for example kqueue is broken on
		92	most BSDs and will not be autodetected unless you explicitly request it
		93	(assuming you know what you are doing). This is the set of backends that
		94	C<EVFLAG_AUTO> will probe for.
		95
69	=item ev_set_allocator (void (cb)(void *ptr, long size))	96	=item ev_set_allocator (void (cb)(void *ptr, long size))
70		97
71	Sets the allocation function to use (the prototype is similar to the	98	Sets the allocation function to use (the prototype is similar to the
72	realloc function). It is used to allocate and free memory (no surprises	99	realloc C function, the semantics are identical). It is used to allocate
73	here). If it returns zero when memory needs to be allocated, the library	100	and free memory (no surprises here). If it returns zero when memory
74	might abort or take some potentially destructive action. The default is	101	needs to be allocated, the library might abort or take some potentially
75	your system realloc function.	102	destructive action. The default is your system realloc function.
76		103
77	You could override this function in high-availability programs to, say,	104	You could override this function in high-availability programs to, say,
78	free some memory if it cannot allocate memory, to use a special allocator,	105	free some memory if it cannot allocate memory, to use a special allocator,
79	or even to sleep a while and retry until some memory is available.	106	or even to sleep a while and retry until some memory is available.
80		107
…		…
82		109
83	Set the callback function to call on a retryable syscall error (such	110	Set the callback function to call on a retryable syscall error (such
84	as failed select, poll, epoll_wait). The message is a printable string	111	as failed select, poll, epoll_wait). The message is a printable string
85	indicating the system call or subsystem causing the problem. If this	112	indicating the system call or subsystem causing the problem. If this
86	callback is set, then libev will expect it to remedy the sitution, no	113	callback is set, then libev will expect it to remedy the sitution, no
87	matter what, when it returns. That is, libev will geenrally retry the	114	matter what, when it returns. That is, libev will generally retry the
88	requested operation, or, if the condition doesn't go away, do bad stuff	115	requested operation, or, if the condition doesn't go away, do bad stuff
89	(such as abort).	116	(such as abort).
90		117
91	=back	118	=back
92		119
…		…
95	An event loop is described by a C<struct ev_loop *>. The library knows two	122	An event loop is described by a C<struct ev_loop *>. The library knows two
96	types of such loops, the I<default> loop, which supports signals and child	123	types of such loops, the I<default> loop, which supports signals and child
97	events, and dynamically created loops which do not.	124	events, and dynamically created loops which do not.
98		125
99	If you use threads, a common model is to run the default event loop	126	If you use threads, a common model is to run the default event loop
100	in your main thread (or in a separate thrad) and for each thread you	127	in your main thread (or in a separate thread) and for each thread you
101	create, you also create another event loop. Libev itself does no lockign	128	create, you also create another event loop. Libev itself does no locking
102	whatsoever, so if you mix calls to different event loops, make sure you	129	whatsoever, so if you mix calls to the same event loop in different
103	lock (this is usually a bad idea, though, even if done right).	130	threads, make sure you lock (this is usually a bad idea, though, even if
		131	done correctly, because it's hideous and inefficient).
104		132
105	=over 4	133	=over 4
106		134
107	=item struct ev_loop *ev_default_loop (unsigned int flags)	135	=item struct ev_loop *ev_default_loop (unsigned int flags)
108		136
109	This will initialise the default event loop if it hasn't been initialised	137	This will initialise the default event loop if it hasn't been initialised
110	yet and return it. If the default loop could not be initialised, returns	138	yet and return it. If the default loop could not be initialised, returns
111	false. If it already was initialised it simply returns it (and ignores the	139	false. If it already was initialised it simply returns it (and ignores the
112	flags).	140	flags. If that is troubling you, check C<ev_backend ()> afterwards).
113		141
114	If you don't know what event loop to use, use the one returned from this	142	If you don't know what event loop to use, use the one returned from this
115	function.	143	function.
116		144
117	The flags argument can be used to specify special behaviour or specific	145	The flags argument can be used to specify special behaviour or specific
118	backends to use, and is usually specified as 0 (or EVFLAG_AUTO)	146	backends to use, and is usually specified as C<0> (or EVFLAG_AUTO).
119		147
120	It supports the following flags:	148	It supports the following flags:
121		149
122	=over 4	150	=over 4
123		151
124	=item EVFLAG_AUTO	152	=item C<EVFLAG_AUTO>
125		153
126	The default flags value. Use this if you have no clue (its the right	154	The default flags value. Use this if you have no clue (it's the right
127	thing, believe me).	155	thing, believe me).
128		156
129	=item EVFLAG_NOENV	157	=item C<EVFLAG_NOENV>
130		158
131	If this flag bit is ored into the flag value then libev will I<not> look	159	If this flag bit is ored into the flag value (or the program runs setuid
132	at the environment variable C<LIBEV_FLAGS>. Otherwise (the default), this	160	or setgid) then libev will I<not> look at the environment variable
133	environment variable will override the flags completely. This is useful	161	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will
		162	override the flags completely if it is found in the environment. This is
134	to try out specific backends to tets their performance, or to work around	163	useful to try out specific backends to test their performance, or to work
135	bugs.	164	around bugs.
136		165
137	=item EVMETHOD_SELECT portable select backend	166	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
138		167
139	=item EVMETHOD_POLL poll backend (everywhere except windows)	168	This is your standard select(2) backend. Not I<completely> standard, as
		169	libev tries to roll its own fd_set with no limits on the number of fds,
		170	but if that fails, expect a fairly low limit on the number of fds when
		171	using this backend. It doesn't scale too well (O(highest_fd)), but its usually
		172	the fastest backend for a low number of fds.
140		173
141	=item EVMETHOD_EPOLL linux only	174	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)
142		175
143	=item EVMETHOD_KQUEUE some bsds only	176	And this is your standard poll(2) backend. It's more complicated than
		177	select, but handles sparse fds better and has no artificial limit on the
		178	number of fds you can use (except it will slow down considerably with a
		179	lot of inactive fds). It scales similarly to select, i.e. O(total_fds).
144		180
145	=item EVMETHOD_DEVPOLL solaris 8 only	181	=item C<EVBACKEND_EPOLL> (value 4, Linux)
146		182
147	=item EVMETHOD_PORT solaris 10 only	183	For few fds, this backend is a bit little slower than poll and select,
		184	but it scales phenomenally better. While poll and select usually scale like
		185	O(total_fds) where n is the total number of fds (or the highest fd), epoll scales
		186	either O(1) or O(active_fds).
		187
		188	While stopping and starting an I/O watcher in the same iteration will
		189	result in some caching, there is still a syscall per such incident
		190	(because the fd could point to a different file description now), so its
		191	best to avoid that. Also, dup()ed file descriptors might not work very
		192	well if you register events for both fds.
		193
		194	=item C<EVBACKEND_KQUEUE> (value 8, most BSD clones)
		195
		196	Kqueue deserves special mention, as at the time of this writing, it
		197	was broken on all BSDs except NetBSD (usually it doesn't work with
		198	anything but sockets and pipes, except on Darwin, where of course its
		199	completely useless). For this reason its not being "autodetected" unless
		200	you explicitly specify the flags (i.e. you don't use EVFLAG_AUTO).
		201
		202	It scales in the same way as the epoll backend, but the interface to the
		203	kernel is more efficient (which says nothing about its actual speed, of
		204	course). While starting and stopping an I/O watcher does not cause an
		205	extra syscall as with epoll, it still adds up to four event changes per
		206	incident, so its best to avoid that.
		207
		208	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)
		209
		210	This is not implemented yet (and might never be).
		211
		212	=item C<EVBACKEND_PORT> (value 32, Solaris 10)
		213
		214	This uses the Solaris 10 port mechanism. As with everything on Solaris,
		215	it's really slow, but it still scales very well (O(active_fds)).
		216
		217	=item C<EVBACKEND_ALL>
		218
		219	Try all backends (even potentially broken ones that wouldn't be tried
		220	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
		221	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.
		222
		223	=back
148		224
149	If one or more of these are ored into the flags value, then only these	225	If one or more of these are ored into the flags value, then only these
150	backends will be tried (in the reverse order as given here). If one are	226	backends will be tried (in the reverse order as given here). If none are
151	specified, any backend will do.	227	specified, most compiled-in backend will be tried, usually in reverse
152		228	order of their flag values :)
153	=back
154		229
155	=item struct ev_loop *ev_loop_new (unsigned int flags)	230	=item struct ev_loop *ev_loop_new (unsigned int flags)
156		231
157	Similar to C<ev_default_loop>, but always creates a new event loop that is	232	Similar to C<ev_default_loop>, but always creates a new event loop that is
158	always distinct from the default loop. Unlike the default loop, it cannot	233	always distinct from the default loop. Unlike the default loop, it cannot
…		…
161		236
162	=item ev_default_destroy ()	237	=item ev_default_destroy ()
163		238
164	Destroys the default loop again (frees all memory and kernel state	239	Destroys the default loop again (frees all memory and kernel state
165	etc.). This stops all registered event watchers (by not touching them in	240	etc.). This stops all registered event watchers (by not touching them in
166	any way whatsoever, although you cnanot rely on this :).	241	any way whatsoever, although you cannot rely on this :).
167		242
168	=item ev_loop_destroy (loop)	243	=item ev_loop_destroy (loop)
169		244
170	Like C<ev_default_destroy>, but destroys an event loop created by an	245	Like C<ev_default_destroy>, but destroys an event loop created by an
171	earlier call to C<ev_loop_new>.	246	earlier call to C<ev_loop_new>.
…		…
175	This function reinitialises the kernel state for backends that have	250	This function reinitialises the kernel state for backends that have
176	one. Despite the name, you can call it anytime, but it makes most sense	251	one. Despite the name, you can call it anytime, but it makes most sense
177	after forking, in either the parent or child process (or both, but that	252	after forking, in either the parent or child process (or both, but that
178	again makes little sense).	253	again makes little sense).
179		254
180	You I<must> call this function after forking if and only if you want to	255	You I<must> call this function in the child process after forking if and
181	use the event library in both processes. If you just fork+exec, you don't	256	only if you want to use the event library in both processes. If you just
182	have to call it.	257	fork+exec, you don't have to call it.
183		258
184	The function itself is quite fast and its usually not a problem to call	259	The function itself is quite fast and it's usually not a problem to call
185	it just in case after a fork. To make this easy, the function will fit in	260	it just in case after a fork. To make this easy, the function will fit in
186	quite nicely into a call to C<pthread_atfork>:	261	quite nicely into a call to C<pthread_atfork>:
187		262
188	pthread_atfork (0, 0, ev_default_fork);	263	pthread_atfork (0, 0, ev_default_fork);
		264
		265	At the moment, C<EVBACKEND_SELECT> and C<EVBACKEND_POLL> are safe to use
		266	without calling this function, so if you force one of those backends you
		267	do not need to care.
189		268
190	=item ev_loop_fork (loop)	269	=item ev_loop_fork (loop)
191		270
192	Like C<ev_default_fork>, but acts on an event loop created by	271	Like C<ev_default_fork>, but acts on an event loop created by
193	C<ev_loop_new>. Yes, you have to call this on every allocated event loop	272	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
194	after fork, and how you do this is entirely your own problem.	273	after fork, and how you do this is entirely your own problem.
195		274
196	=item unsigned int ev_method (loop)	275	=item unsigned int ev_backend (loop)
197		276
198	Returns one of the C<EVMETHOD_*> flags indicating the event backend in	277	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
199	use.	278	use.
200		279
201	=item ev_tstamp = ev_now (loop)	280	=item ev_tstamp ev_now (loop)
202		281
203	Returns the current "event loop time", which is the time the event loop	282	Returns the current "event loop time", which is the time the event loop
204	got events and started processing them. This timestamp does not change	283	got events and started processing them. This timestamp does not change
205	as long as callbacks are being processed, and this is also the base time	284	as long as callbacks are being processed, and this is also the base time
206	used for relative timers. You can treat it as the timestamp of the event	285	used for relative timers. You can treat it as the timestamp of the event
…		…
215	If the flags argument is specified as 0, it will not return until either	294	If the flags argument is specified as 0, it will not return until either
216	no event watchers are active anymore or C<ev_unloop> was called.	295	no event watchers are active anymore or C<ev_unloop> was called.
217		296
218	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle	297	A flags value of C<EVLOOP_NONBLOCK> will look for new events, will handle
219	those events and any outstanding ones, but will not block your process in	298	those events and any outstanding ones, but will not block your process in
220	case there are no events.	299	case there are no events and will return after one iteration of the loop.
221		300
222	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if	301	A flags value of C<EVLOOP_ONESHOT> will look for new events (waiting if
223	neccessary) and will handle those and any outstanding ones. It will block	302	neccessary) and will handle those and any outstanding ones. It will block
224	your process until at least one new event arrives.	303	your process until at least one new event arrives, and will return after
		304	one iteration of the loop.
225		305
226	This flags value could be used to implement alternative looping	306	This flags value could be used to implement alternative looping
227	constructs, but the C<prepare> and C<check> watchers provide a better and	307	constructs, but the C<prepare> and C<check> watchers provide a better and
228	more generic mechanism.	308	more generic mechanism.
229		309
		310	Here are the gory details of what ev_loop does:
		311
		312	1. If there are no active watchers (reference count is zero), return.
		313	2. Queue and immediately call all prepare watchers.
		314	3. If we have been forked, recreate the kernel state.
		315	4. Update the kernel state with all outstanding changes.
		316	5. Update the "event loop time".
		317	6. Calculate for how long to block.
		318	7. Block the process, waiting for events.
		319	8. Update the "event loop time" and do time jump handling.
		320	9. Queue all outstanding timers.
		321	10. Queue all outstanding periodics.
		322	11. If no events are pending now, queue all idle watchers.
		323	12. Queue all check watchers.
		324	13. Call all queued watchers in reverse order (i.e. check watchers first).
		325	14. If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
		326	was used, return, otherwise continue with step #1.
		327
230	=item ev_unloop (loop, how)	328	=item ev_unloop (loop, how)
231		329
232	Can be used to make a call to C<ev_loop> return early. The C<how> argument	330	Can be used to make a call to C<ev_loop> return early (but only after it
		331	has processed all outstanding events). The C<how> argument must be either
233	must be either C<EVUNLOOP_ONCE>, which will make the innermost C<ev_loop>	332	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or
234	call return, or C<EVUNLOOP_ALL>, which will make all nested C<ev_loop>	333	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.
235	calls return.
236		334
237	=item ev_ref (loop)	335	=item ev_ref (loop)
238		336
239	=item ev_unref (loop)	337	=item ev_unref (loop)
240		338
241	Ref/unref can be used to add or remove a refcount on the event loop: Every	339	Ref/unref can be used to add or remove a reference count on the event
242	watcher keeps one reference. If you have a long-runing watcher you never	340	loop: Every watcher keeps one reference, and as long as the reference
243	unregister that should not keep ev_loop from running, ev_unref() after	341	count is nonzero, C<ev_loop> will not return on its own. If you have
244	starting, and ev_ref() before stopping it. Libev itself uses this for	342	a watcher you never unregister that should not keep C<ev_loop> from
245	example for its internal signal pipe: It is not visible to you as a user	343	returning, ev_unref() after starting, and ev_ref() before stopping it. For
246	and should not keep C<ev_loop> from exiting if the work is done. It is	344	example, libev itself uses this for its internal signal pipe: It is not
247	also an excellent way to do this for generic recurring timers or from	345	visible to the libev user and should not keep C<ev_loop> from exiting if
248	within third-party libraries. Just remember to unref after start and ref	346	no event watchers registered by it are active. It is also an excellent
249	before stop.	347	way to do this for generic recurring timers or from within third-party
		348	libraries. Just remember to I<unref after start> and I<ref before stop>.
250		349
251	=back	350	=back
252		351
253	=head1 ANATOMY OF A WATCHER	352	=head1 ANATOMY OF A WATCHER
254		353
255	A watcher is a structure that you create and register to record your	354	A watcher is a structure that you create and register to record your
256	interest in some event. For instance, if you want to wait for STDIN to	355	interest in some event. For instance, if you want to wait for STDIN to
257	become readable, you would create an ev_io watcher for that:	356	become readable, you would create an C<ev_io> watcher for that:
258		357
259	static void my_cb (struct ev_loop loop, struct ev_io w, int revents)	358	static void my_cb (struct ev_loop loop, struct ev_io w, int revents)
260	{	359	{
261	ev_io_stop (w);	360	ev_io_stop (w);
262	ev_unloop (loop, EVUNLOOP_ALL);	361	ev_unloop (loop, EVUNLOOP_ALL);
…		…
289	*) >>), and you can stop watching for events at any time by calling the	388	*) >>), and you can stop watching for events at any time by calling the
290	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.	389	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.
291		390
292	As long as your watcher is active (has been started but not stopped) you	391	As long as your watcher is active (has been started but not stopped) you
293	must not touch the values stored in it. Most specifically you must never	392	must not touch the values stored in it. Most specifically you must never
294	reinitialise it or call its set method.	393	reinitialise it or call its set macro.
295		394
296	You cna check wether an event is active by calling the C<ev_is_active	395	You can check whether an event is active by calling the C<ev_is_active
297	(watcher *)> macro. To see wether an event is outstanding (but the	396	(watcher *)> macro. To see whether an event is outstanding (but the
298	callback for it has not been called yet) you cna use the C<ev_is_pending	397	callback for it has not been called yet) you can use the C<ev_is_pending
299	(watcher *)> macro.	398	(watcher *)> macro.
300		399
301	Each and every callback receives the event loop pointer as first, the	400	Each and every callback receives the event loop pointer as first, the
302	registered watcher structure as second, and a bitset of received events as	401	registered watcher structure as second, and a bitset of received events as
303	third argument.	402	third argument.
304		403
305	The rceeived events usually include a single bit per event type received	404	The received events usually include a single bit per event type received
306	(you can receive multiple events at the same time). The possible bit masks	405	(you can receive multiple events at the same time). The possible bit masks
307	are:	406	are:
308		407
309	=over 4	408	=over 4
310		409
311	=item EV_READ	410	=item C<EV_READ>
312		411
313	=item EV_WRITE	412	=item C<EV_WRITE>
314		413
315	The file descriptor in the ev_io watcher has become readable and/or	414	The file descriptor in the C<ev_io> watcher has become readable and/or
316	writable.	415	writable.
317		416
318	=item EV_TIMEOUT	417	=item C<EV_TIMEOUT>
319		418
320	The ev_timer watcher has timed out.	419	The C<ev_timer> watcher has timed out.
321		420
322	=item EV_PERIODIC	421	=item C<EV_PERIODIC>
323		422
324	The ev_periodic watcher has timed out.	423	The C<ev_periodic> watcher has timed out.
325		424
326	=item EV_SIGNAL	425	=item C<EV_SIGNAL>
327		426
328	The signal specified in the ev_signal watcher has been received by a thread.	427	The signal specified in the C<ev_signal> watcher has been received by a thread.
329		428
330	=item EV_CHILD	429	=item C<EV_CHILD>
331		430
332	The pid specified in the ev_child watcher has received a status change.	431	The pid specified in the C<ev_child> watcher has received a status change.
333		432
334	=item EV_IDLE	433	=item C<EV_IDLE>
335		434
336	The ev_idle watcher has determined that you have nothing better to do.	435	The C<ev_idle> watcher has determined that you have nothing better to do.
337		436
338	=item EV_PREPARE	437	=item C<EV_PREPARE>
339		438
340	=item EV_CHECK	439	=item C<EV_CHECK>
341		440
342	All ev_prepare watchers are invoked just I<before> C<ev_loop> starts	441	All C<ev_prepare> watchers are invoked just I<before> C<ev_loop> starts
343	to gather new events, and all ev_check watchers are invoked just after	442	to gather new events, and all C<ev_check> watchers are invoked just after
344	C<ev_loop> has gathered them, but before it invokes any callbacks for any	443	C<ev_loop> has gathered them, but before it invokes any callbacks for any
345	received events. Callbacks of both watcher types can start and stop as	444	received events. Callbacks of both watcher types can start and stop as
346	many watchers as they want, and all of them will be taken into account	445	many watchers as they want, and all of them will be taken into account
347	(for example, a ev_prepare watcher might start an idle watcher to keep	446	(for example, a C<ev_prepare> watcher might start an idle watcher to keep
348	C<ev_loop> from blocking).	447	C<ev_loop> from blocking).
349		448
350	=item EV_ERROR	449	=item C<EV_ERROR>
351		450
352	An unspecified error has occured, the watcher has been stopped. This might	451	An unspecified error has occured, the watcher has been stopped. This might
353	happen because the watcher could not be properly started because libev	452	happen because the watcher could not be properly started because libev
354	ran out of memory, a file descriptor was found to be closed or any other	453	ran out of memory, a file descriptor was found to be closed or any other
355	problem. You best act on it by reporting the problem and somehow coping	454	problem. You best act on it by reporting the problem and somehow coping
…		…
364	=back	463	=back
365		464
366	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER	465	=head2 ASSOCIATING CUSTOM DATA WITH A WATCHER
367		466
368	Each watcher has, by default, a member C<void *data> that you can change	467	Each watcher has, by default, a member C<void *data> that you can change
369	and read at any time, libev will completely ignore it. This cna be used	468	and read at any time, libev will completely ignore it. This can be used
370	to associate arbitrary data with your watcher. If you need more data and	469	to associate arbitrary data with your watcher. If you need more data and
371	don't want to allocate memory and store a pointer to it in that data	470	don't want to allocate memory and store a pointer to it in that data
372	member, you can also "subclass" the watcher type and provide your own	471	member, you can also "subclass" the watcher type and provide your own
373	data:	472	data:
374		473
…		…
396	=head1 WATCHER TYPES	495	=head1 WATCHER TYPES
397		496
398	This section describes each watcher in detail, but will not repeat	497	This section describes each watcher in detail, but will not repeat
399	information given in the last section.	498	information given in the last section.
400		499
401	=head2 struct ev_io - is my file descriptor readable or writable	500	=head2 C<ev_io> - is this file descriptor readable or writable
402		501
403	I/O watchers check wether a file descriptor is readable or writable	502	I/O watchers check whether a file descriptor is readable or writable
404	in each iteration of the event loop (This behaviour is called	503	in each iteration of the event loop (This behaviour is called
405	level-triggering because you keep receiving events as long as the	504	level-triggering because you keep receiving events as long as the
406	condition persists. Remember you cna stop the watcher if you don't want to	505	condition persists. Remember you can stop the watcher if you don't want to
407	act on the event and neither want to receive future events).	506	act on the event and neither want to receive future events).
408		507
		508	In general you can register as many read and/or write event watchers per
		509	fd as you want (as long as you don't confuse yourself). Setting all file
		510	descriptors to non-blocking mode is also usually a good idea (but not
		511	required if you know what you are doing).
		512
		513	You have to be careful with dup'ed file descriptors, though. Some backends
		514	(the linux epoll backend is a notable example) cannot handle dup'ed file
		515	descriptors correctly if you register interest in two or more fds pointing
		516	to the same underlying file/socket etc. description (that is, they share
		517	the same underlying "file open").
		518
		519	If you must do this, then force the use of a known-to-be-good backend
		520	(at the time of this writing, this includes only C<EVBACKEND_SELECT> and
		521	C<EVBACKEND_POLL>).
		522
409	=over 4	523	=over 4
410		524
411	=item ev_io_init (ev_io *, callback, int fd, int events)	525	=item ev_io_init (ev_io *, callback, int fd, int events)
412		526
413	=item ev_io_set (ev_io *, int fd, int events)	527	=item ev_io_set (ev_io *, int fd, int events)
414		528
415	Configures an ev_io watcher. The fd is the file descriptor to rceeive	529	Configures an C<ev_io> watcher. The fd is the file descriptor to rceeive
416	events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ \|	530	events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ \|
417	EV_WRITE> to receive the given events.	531	EV_WRITE> to receive the given events.
418		532
419	=back	533	=back
420		534
421	=head2 struct ev_timer - relative and optionally recurring timeouts	535	=head2 C<ev_timer> - relative and optionally recurring timeouts
422		536
423	Timer watchers are simple relative timers that generate an event after a	537	Timer watchers are simple relative timers that generate an event after a
424	given time, and optionally repeating in regular intervals after that.	538	given time, and optionally repeating in regular intervals after that.
425		539
426	The timers are based on real time, that is, if you register an event that	540	The timers are based on real time, that is, if you register an event that
427	times out after an hour and youreset your system clock to last years	541	times out after an hour and you reset your system clock to last years
428	time, it will still time out after (roughly) and hour. "Roughly" because	542	time, it will still time out after (roughly) and hour. "Roughly" because
429	detecting time jumps is hard, and soem inaccuracies are unavoidable (the	543	detecting time jumps is hard, and some inaccuracies are unavoidable (the
430	monotonic clock option helps a lot here).	544	monotonic clock option helps a lot here).
		545
		546	The relative timeouts are calculated relative to the C<ev_now ()>
		547	time. This is usually the right thing as this timestamp refers to the time
		548	of the event triggering whatever timeout you are modifying/starting. If
		549	you suspect event processing to be delayed and you I<need> to base the timeout
		550	on the current time, use something like this to adjust for this:
		551
		552	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);
		553
		554	The callback is guarenteed to be invoked only when its timeout has passed,
		555	but if multiple timers become ready during the same loop iteration then
		556	order of execution is undefined.
431		557
432	=over 4	558	=over 4
433		559
434	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)	560	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)
435		561
…		…
441	later, again, and again, until stopped manually.	567	later, again, and again, until stopped manually.
442		568
443	The timer itself will do a best-effort at avoiding drift, that is, if you	569	The timer itself will do a best-effort at avoiding drift, that is, if you
444	configure a timer to trigger every 10 seconds, then it will trigger at	570	configure a timer to trigger every 10 seconds, then it will trigger at
445	exactly 10 second intervals. If, however, your program cannot keep up with	571	exactly 10 second intervals. If, however, your program cannot keep up with
446	the timer (ecause it takes longer than those 10 seconds to do stuff) the	572	the timer (because it takes longer than those 10 seconds to do stuff) the
447	timer will not fire more than once per event loop iteration.	573	timer will not fire more than once per event loop iteration.
448		574
449	=item ev_timer_again (loop)	575	=item ev_timer_again (loop)
450		576
451	This will act as if the timer timed out and restart it again if it is	577	This will act as if the timer timed out and restart it again if it is
…		…
458		584
459	This sounds a bit complicated, but here is a useful and typical	585	This sounds a bit complicated, but here is a useful and typical
460	example: Imagine you have a tcp connection and you want a so-called idle	586	example: Imagine you have a tcp connection and you want a so-called idle
461	timeout, that is, you want to be called when there have been, say, 60	587	timeout, that is, you want to be called when there have been, say, 60
462	seconds of inactivity on the socket. The easiest way to do this is to	588	seconds of inactivity on the socket. The easiest way to do this is to
463	configure an ev_timer with after=repeat=60 and calling ev_timer_again each	589	configure an C<ev_timer> with after=repeat=60 and calling ev_timer_again each
464	time you successfully read or write some data. If you go into an idle	590	time you successfully read or write some data. If you go into an idle
465	state where you do not expect data to travel on the socket, you can stop	591	state where you do not expect data to travel on the socket, you can stop
466	the timer, and again will automatically restart it if need be.	592	the timer, and again will automatically restart it if need be.
467		593
468	=back	594	=back
469		595
470	=head2 ev_periodic	596	=head2 C<ev_periodic> - to cron or not to cron
471		597
472	Periodic watchers are also timers of a kind, but they are very versatile	598	Periodic watchers are also timers of a kind, but they are very versatile
473	(and unfortunately a bit complex).	599	(and unfortunately a bit complex).
474		600
475	Unlike ev_timer's, they are not based on real time (or relative time)	601	Unlike C<ev_timer>'s, they are not based on real time (or relative time)
476	but on wallclock time (absolute time). You can tell a periodic watcher	602	but on wallclock time (absolute time). You can tell a periodic watcher
477	to trigger "at" some specific point in time. For example, if you tell a	603	to trigger "at" some specific point in time. For example, if you tell a
478	periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now ()	604	periodic watcher to trigger in 10 seconds (by specifiying e.g. c<ev_now ()
479	+ 10.>) and then reset your system clock to the last year, then it will	605	+ 10.>) and then reset your system clock to the last year, then it will
480	take a year to trigger the event (unlike an ev_timer, which would trigger	606	take a year to trigger the event (unlike an C<ev_timer>, which would trigger
481	roughly 10 seconds later and of course not if you reset your system time	607	roughly 10 seconds later and of course not if you reset your system time
482	again).	608	again).
483		609
484	They can also be used to implement vastly more complex timers, such as	610	They can also be used to implement vastly more complex timers, such as
485	triggering an event on eahc midnight, local time.	611	triggering an event on eahc midnight, local time.
486		612
		613	As with timers, the callback is guarenteed to be invoked only when the
		614	time (C<at>) has been passed, but if multiple periodic timers become ready
		615	during the same loop iteration then order of execution is undefined.
		616
487	=over 4	617	=over 4
488		618
489	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)	619	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)
490		620
491	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)	621	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)
492		622
493	Lots of arguments, lets sort it out... There are basically three modes of	623	Lots of arguments, lets sort it out... There are basically three modes of
494	operation, and we will explain them from simplest to complex:	624	operation, and we will explain them from simplest to complex:
495
496		625
497	=over 4	626	=over 4
498		627
499	=item * absolute timer (interval = reschedule_cb = 0)	628	=item * absolute timer (interval = reschedule_cb = 0)
500		629
…		…
514		643
515	ev_periodic_set (&periodic, 0., 3600., 0);	644	ev_periodic_set (&periodic, 0., 3600., 0);
516		645
517	This doesn't mean there will always be 3600 seconds in between triggers,	646	This doesn't mean there will always be 3600 seconds in between triggers,
518	but only that the the callback will be called when the system time shows a	647	but only that the the callback will be called when the system time shows a
519	full hour (UTC), or more correct, when the system time is evenly divisible	648	full hour (UTC), or more correctly, when the system time is evenly divisible
520	by 3600.	649	by 3600.
521		650
522	Another way to think about it (for the mathematically inclined) is that	651	Another way to think about it (for the mathematically inclined) is that
523	ev_periodic will try to run the callback in this mode at the next possible	652	C<ev_periodic> will try to run the callback in this mode at the next possible
524	time where C<time = at (mod interval)>, regardless of any time jumps.	653	time where C<time = at (mod interval)>, regardless of any time jumps.
525		654
526	=item * manual reschedule mode (reschedule_cb = callback)	655	=item * manual reschedule mode (reschedule_cb = callback)
527		656
528	In this mode the values for C<interval> and C<at> are both being	657	In this mode the values for C<interval> and C<at> are both being
529	ignored. Instead, each time the periodic watcher gets scheduled, the	658	ignored. Instead, each time the periodic watcher gets scheduled, the
530	reschedule callback will be called with the watcher as first, and the	659	reschedule callback will be called with the watcher as first, and the
531	current time as second argument.	660	current time as second argument.
532		661
533	NOTE: I<This callback MUST NOT stop or destroy the periodic or any other	662	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,
534	periodic watcher, ever, or make any event loop modificstions>. If you need	663	ever, or make any event loop modifications>. If you need to stop it,
535	to stop it, return 1e30 (or so, fudge fudge) and stop it afterwards.	664	return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by
		665	starting a prepare watcher).
536		666
537	Its prototype is c<ev_tstamp (reschedule_cb)(struct ev_periodic w,	667	Its prototype is C<ev_tstamp (reschedule_cb)(struct ev_periodic w,
538	ev_tstamp now)>, e.g.:	668	ev_tstamp now)>, e.g.:
539		669
540	static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)	670	static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)
541	{	671	{
542	return now + 60.;	672	return now + 60.;
…		…
545	It must return the next time to trigger, based on the passed time value	675	It must return the next time to trigger, based on the passed time value
546	(that is, the lowest time value larger than to the second argument). It	676	(that is, the lowest time value larger than to the second argument). It
547	will usually be called just before the callback will be triggered, but	677	will usually be called just before the callback will be triggered, but
548	might be called at other times, too.	678	might be called at other times, too.
549		679
		680	NOTE: I<< This callback must always return a time that is later than the
		681	passed C<now> value >>. Not even C<now> itself will do, it I<must> be larger.
		682
550	This can be used to create very complex timers, such as a timer that	683	This can be used to create very complex timers, such as a timer that
551	triggers on each midnight, local time. To do this, you would calculate the	684	triggers on each midnight, local time. To do this, you would calculate the
552	next midnight after C<now> and return the timestamp value for this. How you do this	685	next midnight after C<now> and return the timestamp value for this. How
553	is, again, up to you (but it is not trivial).	686	you do this is, again, up to you (but it is not trivial, which is the main
		687	reason I omitted it as an example).
554		688
555	=back	689	=back
556		690
557	=item ev_periodic_again (loop, ev_periodic *)	691	=item ev_periodic_again (loop, ev_periodic *)
558		692
…		…
561	a different time than the last time it was called (e.g. in a crond like	695	a different time than the last time it was called (e.g. in a crond like
562	program when the crontabs have changed).	696	program when the crontabs have changed).
563		697
564	=back	698	=back
565		699
566	=head2 ev_signal - signal me when a signal gets signalled	700	=head2 C<ev_signal> - signal me when a signal gets signalled
567		701
568	Signal watchers will trigger an event when the process receives a specific	702	Signal watchers will trigger an event when the process receives a specific
569	signal one or more times. Even though signals are very asynchronous, libev	703	signal one or more times. Even though signals are very asynchronous, libev
570	will try its best to deliver signals synchronously, i.e. as part of the	704	will try it's best to deliver signals synchronously, i.e. as part of the
571	normal event processing, like any other event.	705	normal event processing, like any other event.
572		706
573	You cna configure as many watchers as you like per signal. Only when the	707	You can configure as many watchers as you like per signal. Only when the
574	first watcher gets started will libev actually register a signal watcher	708	first watcher gets started will libev actually register a signal watcher
575	with the kernel (thus it coexists with your own signal handlers as long	709	with the kernel (thus it coexists with your own signal handlers as long
576	as you don't register any with libev). Similarly, when the last signal	710	as you don't register any with libev). Similarly, when the last signal
577	watcher for a signal is stopped libev will reset the signal handler to	711	watcher for a signal is stopped libev will reset the signal handler to
578	SIG_DFL (regardless of what it was set to before).	712	SIG_DFL (regardless of what it was set to before).
…		…
586	Configures the watcher to trigger on the given signal number (usually one	720	Configures the watcher to trigger on the given signal number (usually one
587	of the C<SIGxxx> constants).	721	of the C<SIGxxx> constants).
588		722
589	=back	723	=back
590		724
591	=head2 ev_child - wait for pid status changes	725	=head2 C<ev_child> - wait for pid status changes
592		726
593	Child watchers trigger when your process receives a SIGCHLD in response to	727	Child watchers trigger when your process receives a SIGCHLD in response to
594	some child status changes (most typically when a child of yours dies).	728	some child status changes (most typically when a child of yours dies).
595		729
596	=over 4	730	=over 4
…		…
600	=item ev_child_set (ev_child *, int pid)	734	=item ev_child_set (ev_child *, int pid)
601		735
602	Configures the watcher to wait for status changes of process C<pid> (or	736	Configures the watcher to wait for status changes of process C<pid> (or
603	I<any> process if C<pid> is specified as C<0>). The callback can look	737	I<any> process if C<pid> is specified as C<0>). The callback can look
604	at the C<rstatus> member of the C<ev_child> watcher structure to see	738	at the C<rstatus> member of the C<ev_child> watcher structure to see
605	the status word (use the macros from C<sys/wait.h>). The C<rpid> member	739	the status word (use the macros from C<sys/wait.h> and see your systems
606	contains the pid of the process causing the status change.	740	C<waitpid> documentation). The C<rpid> member contains the pid of the
		741	process causing the status change.
607		742
608	=back	743	=back
609		744
610	=head2 ev_idle - when you've got nothing better to do	745	=head2 C<ev_idle> - when you've got nothing better to do
611		746
612	Idle watchers trigger events when there are no other I/O or timer (or	747	Idle watchers trigger events when there are no other events are pending
613	periodic) events pending. That is, as long as your process is busy	748	(prepare, check and other idle watchers do not count). That is, as long
614	handling sockets or timeouts it will not be called. But when your process	749	as your process is busy handling sockets or timeouts (or even signals,
615	is idle all idle watchers are being called again and again - until	750	imagine) it will not be triggered. But when your process is idle all idle
		751	watchers are being called again and again, once per event loop iteration -
616	stopped, that is, or your process receives more events.	752	until stopped, that is, or your process receives more events and becomes
		753	busy.
617		754
618	The most noteworthy effect is that as long as any idle watchers are	755	The most noteworthy effect is that as long as any idle watchers are
619	active, the process will not block when waiting for new events.	756	active, the process will not block when waiting for new events.
620		757
621	Apart from keeping your process non-blocking (which is a useful	758	Apart from keeping your process non-blocking (which is a useful
…		…
631	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,	768	kind. There is a C<ev_idle_set> macro, but using it is utterly pointless,
632	believe me.	769	believe me.
633		770
634	=back	771	=back
635		772
636	=head2 prepare and check - your hooks into the event loop	773	=head2 C<ev_prepare> and C<ev_check> - customise your event loop
637		774
638	Prepare and check watchers usually (but not always) are used in	775	Prepare and check watchers are usually (but not always) used in tandem:
639	tandom. Prepare watchers get invoked before the process blocks and check	776	prepare watchers get invoked before the process blocks and check watchers
640	watchers afterwards.	777	afterwards.
641		778
642	Their main purpose is to integrate other event mechanisms into libev. This	779	Their main purpose is to integrate other event mechanisms into libev. This
643	could be used, for example, to track variable changes, implement your own	780	could be used, for example, to track variable changes, implement your own
644	watchers, integrate net-snmp or a coroutine library and lots more.	781	watchers, integrate net-snmp or a coroutine library and lots more.
645		782
646	This is done by examining in each prepare call which file descriptors need	783	This is done by examining in each prepare call which file descriptors need
647	to be watched by the other library, registering ev_io watchers for them	784	to be watched by the other library, registering C<ev_io> watchers for
648	and starting an ev_timer watcher for any timeouts (many libraries provide	785	them and starting an C<ev_timer> watcher for any timeouts (many libraries
649	just this functionality). Then, in the check watcher you check for any	786	provide just this functionality). Then, in the check watcher you check for
650	events that occured (by making your callbacks set soem flags for example)	787	any events that occured (by checking the pending status of all watchers
651	and call back into the library.	788	and stopping them) and call back into the library. The I/O and timer
		789	callbacks will never actually be called (but must be valid nevertheless,
		790	because you never know, you know?).
652		791
653	As another example, the perl Coro module uses these hooks to integrate	792	As another example, the Perl Coro module uses these hooks to integrate
654	coroutines into libev programs, by yielding to other active coroutines	793	coroutines into libev programs, by yielding to other active coroutines
655	during each prepare and only letting the process block if no coroutines	794	during each prepare and only letting the process block if no coroutines
656	are ready to run.	795	are ready to run (it's actually more complicated: it only runs coroutines
		796	with priority higher than or equal to the event loop and one coroutine
		797	of lower priority, but only once, using idle watchers to keep the event
		798	loop from blocking if lower-priority coroutines are active, thus mapping
		799	low-priority coroutines to idle/background tasks).
657		800
658	=over 4	801	=over 4
659		802
660	=item ev_prepare_init (ev_prepare *, callback)	803	=item ev_prepare_init (ev_prepare *, callback)
661		804
662	=item ev_check_init (ev_check *, callback)	805	=item ev_check_init (ev_check *, callback)
663		806
664	Initialises and configures the prepare or check watcher - they have no	807	Initialises and configures the prepare or check watcher - they have no
665	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>	808	parameters of any kind. There are C<ev_prepare_set> and C<ev_check_set>
666	macros, but using them is utterly, utterly pointless.	809	macros, but using them is utterly, utterly and completely pointless.
667		810
668	=back	811	=back
669		812
670	=head1 OTHER FUNCTIONS	813	=head1 OTHER FUNCTIONS
671		814
672	There are some other fucntions of possible interest. Described. Here. Now.	815	There are some other functions of possible interest. Described. Here. Now.
673		816
674	=over 4	817	=over 4
675		818
676	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)	819	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)
677		820
678	This function combines a simple timer and an I/O watcher, calls your	821	This function combines a simple timer and an I/O watcher, calls your
679	callback on whichever event happens first and automatically stop both	822	callback on whichever event happens first and automatically stop both
680	watchers. This is useful if you want to wait for a single event on an fd	823	watchers. This is useful if you want to wait for a single event on an fd
681	or timeout without havign to allocate/configure/start/stop/free one or	824	or timeout without having to allocate/configure/start/stop/free one or
682	more watchers yourself.	825	more watchers yourself.
683		826
684	If C<fd> is less than 0, then no I/O watcher will be started and events is	827	If C<fd> is less than 0, then no I/O watcher will be started and events
685	ignored. Otherwise, an ev_io watcher for the given C<fd> and C<events> set	828	is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and
686	will be craeted and started.	829	C<events> set will be craeted and started.
687		830
688	If C<timeout> is less than 0, then no timeout watcher will be	831	If C<timeout> is less than 0, then no timeout watcher will be
689	started. Otherwise an ev_timer watcher with after = C<timeout> (and repeat	832	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and
690	= 0) will be started.	833	repeat = 0) will be started. While C<0> is a valid timeout, it is of
		834	dubious value.
691		835
692	The callback has the type C<void (cb)(int revents, void arg)> and	836	The callback has the type C<void (cb)(int revents, void arg)> and gets
693	gets passed an events set (normally a combination of EV_ERROR, EV_READ,	837	passed an C<revents> set like normal event callbacks (a combination of
694	EV_WRITE or EV_TIMEOUT) and the C<arg> value passed to C<ev_once>:	838	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>
		839	value passed to C<ev_once>:
695		840
696	static void stdin_ready (int revents, void *arg)	841	static void stdin_ready (int revents, void *arg)
697	{	842	{
698	if (revents & EV_TIMEOUT)	843	if (revents & EV_TIMEOUT)
699	/* doh, nothing entered */	844	/* doh, nothing entered */;
700	else if (revents & EV_READ)	845	else if (revents & EV_READ)
701	/* stdin might have data for us, joy! */	846	/* stdin might have data for us, joy! */;
702	}	847	}
703		848
704	ev_once (STDIN_FILENO, EV_READm 10., stdin_ready, 0);	849	ev_once (STDIN_FILENO, EV_READ, 10., stdin_ready, 0);
705		850
706	=item ev_feed_event (loop, watcher, int events)	851	=item ev_feed_event (loop, watcher, int events)
707		852
708	Feeds the given event set into the event loop, as if the specified event	853	Feeds the given event set into the event loop, as if the specified event
709	has happened for the specified watcher (which must be a pointer to an	854	had happened for the specified watcher (which must be a pointer to an
710	initialised but not necessarily active event watcher).	855	initialised but not necessarily started event watcher).
711		856
712	=item ev_feed_fd_event (loop, int fd, int revents)	857	=item ev_feed_fd_event (loop, int fd, int revents)
713		858
714	Feed an event on the given fd, as if a file descriptor backend detected it.	859	Feed an event on the given fd, as if a file descriptor backend detected
		860	the given events it.
715		861
716	=item ev_feed_signal_event (loop, int signum)	862	=item ev_feed_signal_event (loop, int signum)
717		863
718	Feed an event as if the given signal occured (loop must be the default loop!).	864	Feed an event as if the given signal occured (loop must be the default loop!).
719		865
720	=back	866	=back
721		867
		868	=head1 LIBEVENT EMULATION
		869
		870	Libev offers a compatibility emulation layer for libevent. It cannot
		871	emulate the internals of libevent, so here are some usage hints:
		872
		873	=over 4
		874
		875	=item * Use it by including <event.h>, as usual.
		876
		877	=item * The following members are fully supported: ev_base, ev_callback,
		878	ev_arg, ev_fd, ev_res, ev_events.
		879
		880	=item * Avoid using ev_flags and the EVLIST_*-macros, while it is
		881	maintained by libev, it does not work exactly the same way as in libevent (consider
		882	it a private API).
		883
		884	=item * Priorities are not currently supported. Initialising priorities
		885	will fail and all watchers will have the same priority, even though there
		886	is an ev_pri field.
		887
		888	=item * Other members are not supported.
		889
		890	=item * The libev emulation is I<not> ABI compatible to libevent, you need
		891	to use the libev header file and library.
		892
		893	=back
		894
		895	=head1 C++ SUPPORT
		896
		897	TBD.
		898
722	=head1 AUTHOR	899	=head1 AUTHOR
723		900
724	Marc Lehmann <libev@schmorp.de>.	901	Marc Lehmann <libev@schmorp.de>.
725		902

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.1 by root, Mon Nov 12 07:58:13 2007 UTC vs. Revision 1.31 by root, Fri Nov 23 05:00:45 2007 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.1 by root, Mon Nov 12 07:58:13 2007 UTC vs.
Revision 1.31 by root, Fri Nov 23 05:00:45 2007 UTC