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

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.30 by root, Fri Nov 23 04:36:03 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.30 by root, Fri Nov 23 04:36:03 2007 UTC