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

Comparing libev/ev.pod (file contents):
Revision 1.6 by root, Mon Nov 12 08:12:14 2007 UTC vs.
Revision 1.33 by root, Fri Nov 23 15:26:08 2007 UTC

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

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.6 by root, Mon Nov 12 08:12:14 2007 UTC vs. Revision 1.33 by root, Fri Nov 23 15:26:08 2007 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.6 by root, Mon Nov 12 08:12:14 2007 UTC vs.
Revision 1.33 by root, Fri Nov 23 15:26:08 2007 UTC