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

Comparing libev/ev.pod (file contents):
Revision 1.17 by root, Mon Nov 12 08:57:03 2007 UTC vs.
Revision 1.32 by root, Fri Nov 23 08:36:35 2007 UTC

…		…
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	52	=head1 GLOBAL FUNCTIONS
53		53
		54	These functions can be called anytime, even before initialising the
		55	library in any way.
		56
54	=over 4	57	=over 4
55		58
56	=item ev_tstamp ev_time ()	59	=item ev_tstamp ev_time ()
57		60
58	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.
59		64
60	=item int ev_version_major ()	65	=item int ev_version_major ()
61		66
62	=item int ev_version_minor ()	67	=item int ev_version_minor ()
63		68
…		…
69		74
70	Usually, it's a good idea to terminate if the major versions mismatch,	75	Usually, it's a good idea to terminate if the major versions mismatch,
71	as this indicates an incompatible change. Minor versions are usually	76	as this indicates an incompatible change. Minor versions are usually
72	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
73	not a problem.	78	not a problem.
		79
		80	=item unsigned int ev_supported_backends ()
		81
		82	Return the set of all backends (i.e. their corresponding C<EV_BACKEND_*>
		83	value) compiled into this binary of libev (independent of their
		84	availability on the system you are running on). See C<ev_default_loop> for
		85	a description of the set values.
		86
		87	=item unsigned int ev_recommended_backends ()
		88
		89	Return the set of all backends compiled into this binary of libev and also
		90	recommended for this platform. This set is often smaller than the one
		91	returned by C<ev_supported_backends>, as for example kqueue is broken on
		92	most BSDs and will not be autodetected unless you explicitly request it
		93	(assuming you know what you are doing). This is the set of backends that
		94	C<EVFLAG_AUTO> will probe for.
74		95
75	=item ev_set_allocator (void (cb)(void *ptr, long size))	96	=item ev_set_allocator (void (cb)(void *ptr, long size))
76		97
77	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
78	realloc C function, the semantics are identical). It is used to allocate	99	realloc C function, the semantics are identical). It is used to allocate
…		…
114	=item struct ev_loop *ev_default_loop (unsigned int flags)	135	=item struct ev_loop *ev_default_loop (unsigned int flags)
115		136
116	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
117	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
118	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
119	flags).	140	flags. If that is troubling you, check C<ev_backend ()> afterwards).
120		141
121	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
122	function.	143	function.
123		144
124	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
125	backends to use, and is usually specified as 0 (or EVFLAG_AUTO).	146	backends to use, and is usually specified as C<0> (or EVFLAG_AUTO).
126		147
127	It supports the following flags:	148	It supports the following flags:
128		149
129	=over 4	150	=over 4
130		151
…		…
140	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will	161	C<LIBEV_FLAGS>. Otherwise (the default), this environment variable will
141	override the flags completely if it is found in the environment. This is	162	override the flags completely if it is found in the environment. This is
142	useful to try out specific backends to test their performance, or to work	163	useful to try out specific backends to test their performance, or to work
143	around bugs.	164	around bugs.
144		165
145	=item C<EVMETHOD_SELECT> (portable select backend)	166	=item C<EVBACKEND_SELECT> (value 1, portable select backend)
146		167
		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.
		173
147	=item C<EVMETHOD_POLL> (poll backend, available everywhere except on windows)	174	=item C<EVBACKEND_POLL> (value 2, poll backend, available everywhere except on windows)
148		175
149	=item C<EVMETHOD_EPOLL> (linux 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).
150		180
151	=item C<EVMETHOD_KQUEUE> (some bsds only)	181	=item C<EVBACKEND_EPOLL> (value 4, Linux)
152		182
153	=item C<EVMETHOD_DEVPOLL> (solaris 8 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).
154		187
155	=item C<EVMETHOD_PORT> (solaris 10 only)	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" unless
		204	you explicitly specify the flags (i.e. you don't use EVFLAG_AUTO).
		205
		206	It scales in the same way as the epoll backend, but the interface to the
		207	kernel is more efficient (which says nothing about its actual speed, of
		208	course). While starting and stopping an I/O watcher does not cause an
		209	extra syscall as with epoll, it still adds up to four event changes per
		210	incident, so its best to avoid that.
		211
		212	=item C<EVBACKEND_DEVPOLL> (value 16, Solaris 8)
		213
		214	This is not implemented yet (and might never be).
		215
		216	=item C<EVBACKEND_PORT> (value 32, Solaris 10)
		217
		218	This uses the Solaris 10 port mechanism. As with everything on Solaris,
		219	it's really slow, but it still scales very well (O(active_fds)).
		220
		221	Please note that solaris ports can result in a lot of spurious
		222	notifications, so you need to use non-blocking I/O or other means to avoid
		223	blocking when no data (or space) is available.
		224
		225	=item C<EVBACKEND_ALL>
		226
		227	Try all backends (even potentially broken ones that wouldn't be tried
		228	with C<EVFLAG_AUTO>). Since this is a mask, you can do stuff such as
		229	C<EVBACKEND_ALL & ~EVBACKEND_KQUEUE>.
		230
		231	=back
156		232
157	If one or more of these are ored into the flags value, then only these	233	If one or more of these are ored into the flags value, then only these
158	backends will be tried (in the reverse order as given here). If one are	234	backends will be tried (in the reverse order as given here). If none are
159	specified, any backend will do.	235	specified, most compiled-in backend will be tried, usually in reverse
160		236	order of their flag values :)
161	=back
162		237
163	=item struct ev_loop *ev_loop_new (unsigned int flags)	238	=item struct ev_loop *ev_loop_new (unsigned int flags)
164		239
165	Similar to C<ev_default_loop>, but always creates a new event loop that is	240	Similar to C<ev_default_loop>, but always creates a new event loop that is
166	always distinct from the default loop. Unlike the default loop, it cannot	241	always distinct from the default loop. Unlike the default loop, it cannot
…		…
183	This function reinitialises the kernel state for backends that have	258	This function reinitialises the kernel state for backends that have
184	one. Despite the name, you can call it anytime, but it makes most sense	259	one. Despite the name, you can call it anytime, but it makes most sense
185	after forking, in either the parent or child process (or both, but that	260	after forking, in either the parent or child process (or both, but that
186	again makes little sense).	261	again makes little sense).
187		262
188	You I<must> call this function after forking if and only if you want to	263	You I<must> call this function in the child process after forking if and
189	use the event library in both processes. If you just fork+exec, you don't	264	only if you want to use the event library in both processes. If you just
190	have to call it.	265	fork+exec, you don't have to call it.
191		266
192	The function itself is quite fast and it's usually not a problem to call	267	The function itself is quite fast and it's usually not a problem to call
193	it just in case after a fork. To make this easy, the function will fit in	268	it just in case after a fork. To make this easy, the function will fit in
194	quite nicely into a call to C<pthread_atfork>:	269	quite nicely into a call to C<pthread_atfork>:
195		270
196	pthread_atfork (0, 0, ev_default_fork);	271	pthread_atfork (0, 0, ev_default_fork);
197		272
		273	At the moment, C<EVBACKEND_SELECT> and C<EVBACKEND_POLL> are safe to use
		274	without calling this function, so if you force one of those backends you
		275	do not need to care.
		276
198	=item ev_loop_fork (loop)	277	=item ev_loop_fork (loop)
199		278
200	Like C<ev_default_fork>, but acts on an event loop created by	279	Like C<ev_default_fork>, but acts on an event loop created by
201	C<ev_loop_new>. Yes, you have to call this on every allocated event loop	280	C<ev_loop_new>. Yes, you have to call this on every allocated event loop
202	after fork, and how you do this is entirely your own problem.	281	after fork, and how you do this is entirely your own problem.
203		282
204	=item unsigned int ev_method (loop)	283	=item unsigned int ev_backend (loop)
205		284
206	Returns one of the C<EVMETHOD_*> flags indicating the event backend in	285	Returns one of the C<EVBACKEND_*> flags indicating the event backend in
207	use.	286	use.
208		287
209	=item ev_tstamp ev_now (loop)	288	=item ev_tstamp ev_now (loop)
210		289
211	Returns the current "event loop time", which is the time the event loop	290	Returns the current "event loop time", which is the time the event loop
…		…
234		313
235	This flags value could be used to implement alternative looping	314	This flags value could be used to implement alternative looping
236	constructs, but the C<prepare> and C<check> watchers provide a better and	315	constructs, but the C<prepare> and C<check> watchers provide a better and
237	more generic mechanism.	316	more generic mechanism.
238		317
		318	Here are the gory details of what ev_loop does:
		319
		320	1. If there are no active watchers (reference count is zero), return.
		321	2. Queue and immediately call all prepare watchers.
		322	3. If we have been forked, recreate the kernel state.
		323	4. Update the kernel state with all outstanding changes.
		324	5. Update the "event loop time".
		325	6. Calculate for how long to block.
		326	7. Block the process, waiting for events.
		327	8. Update the "event loop time" and do time jump handling.
		328	9. Queue all outstanding timers.
		329	10. Queue all outstanding periodics.
		330	11. If no events are pending now, queue all idle watchers.
		331	12. Queue all check watchers.
		332	13. Call all queued watchers in reverse order (i.e. check watchers first).
		333	14. If ev_unloop has been called or EVLOOP_ONESHOT or EVLOOP_NONBLOCK
		334	was used, return, otherwise continue with step #1.
		335
239	=item ev_unloop (loop, how)	336	=item ev_unloop (loop, how)
240		337
241	Can be used to make a call to C<ev_loop> return early (but only after it	338	Can be used to make a call to C<ev_loop> return early (but only after it
242	has processed all outstanding events). The C<how> argument must be either	339	has processed all outstanding events). The C<how> argument must be either
243	C<EVUNLOOP_ONCE>, which will make the innermost C<ev_loop> call return, or	340	C<EVUNLOOP_ONE>, which will make the innermost C<ev_loop> call return, or
244	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.	341	C<EVUNLOOP_ALL>, which will make all nested C<ev_loop> calls return.
245		342
246	=item ev_ref (loop)	343	=item ev_ref (loop)
247		344
248	=item ev_unref (loop)	345	=item ev_unref (loop)
…		…
299	*) >>), and you can stop watching for events at any time by calling the	396	*) >>), and you can stop watching for events at any time by calling the
300	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.	397	corresponding stop function (C<< ev_<type>_stop (loop, watcher *) >>.
301		398
302	As long as your watcher is active (has been started but not stopped) you	399	As long as your watcher is active (has been started but not stopped) you
303	must not touch the values stored in it. Most specifically you must never	400	must not touch the values stored in it. Most specifically you must never
304	reinitialise it or call its set method.	401	reinitialise it or call its set macro.
305		402
306	You can check whether an event is active by calling the C<ev_is_active	403	You can check whether an event is active by calling the C<ev_is_active
307	(watcher *)> macro. To see whether an event is outstanding (but the	404	(watcher *)> macro. To see whether an event is outstanding (but the
308	callback for it has not been called yet) you can use the C<ev_is_pending	405	callback for it has not been called yet) you can use the C<ev_is_pending
309	(watcher *)> macro.	406	(watcher *)> macro.
…		…
414	in each iteration of the event loop (This behaviour is called	511	in each iteration of the event loop (This behaviour is called
415	level-triggering because you keep receiving events as long as the	512	level-triggering because you keep receiving events as long as the
416	condition persists. Remember you can stop the watcher if you don't want to	513	condition persists. Remember you can stop the watcher if you don't want to
417	act on the event and neither want to receive future events).	514	act on the event and neither want to receive future events).
418		515
419	In general you can register as many read and/or write event watchers oer	516	In general you can register as many read and/or write event watchers per
420	fd as you want (as long as you don't confuse yourself). Setting all file	517	fd as you want (as long as you don't confuse yourself). Setting all file
421	descriptors to non-blocking mode is also usually a good idea (but not	518	descriptors to non-blocking mode is also usually a good idea (but not
422	required if you know what you are doing).	519	required if you know what you are doing).
423		520
424	You have to be careful with dup'ed file descriptors, though. Some backends	521	You have to be careful with dup'ed file descriptors, though. Some backends
425	(the linux epoll backend is a notable example) cannot handle dup'ed file	522	(the linux epoll backend is a notable example) cannot handle dup'ed file
426	descriptors correctly if you register interest in two or more fds pointing	523	descriptors correctly if you register interest in two or more fds pointing
427	to the same file/socket etc. description.	524	to the same underlying file/socket etc. description (that is, they share
		525	the same underlying "file open").
428		526
429	If you must do this, then force the use of a known-to-be-good backend	527	If you must do this, then force the use of a known-to-be-good backend
430	(at the time of this writing, this includes only EVMETHOD_SELECT and	528	(at the time of this writing, this includes only C<EVBACKEND_SELECT> and
431	EVMETHOD_POLL).	529	C<EVBACKEND_POLL>).
432		530
433	=over 4	531	=over 4
434		532
435	=item ev_io_init (ev_io *, callback, int fd, int events)	533	=item ev_io_init (ev_io *, callback, int fd, int events)
436		534
…		…
438		536
439	Configures an C<ev_io> watcher. The fd is the file descriptor to rceeive	537	Configures an C<ev_io> watcher. The fd is the file descriptor to rceeive
440	events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ \|	538	events for and events is either C<EV_READ>, C<EV_WRITE> or C<EV_READ \|
441	EV_WRITE> to receive the given events.	539	EV_WRITE> to receive the given events.
442		540
		541	Please note that most of the more scalable backend mechanisms (for example
		542	epoll and solaris ports) can result in spurious readyness notifications
		543	for file descriptors, so you practically need to use non-blocking I/O (and
		544	treat callback invocation as hint only), or retest separately with a safe
		545	interface before doing I/O (XLib can do this), or force the use of either
		546	C<EVBACKEND_SELECT> or C<EVBACKEND_POLL>, which don't suffer from this
		547	problem. Also note that it is quite easy to have your callback invoked
		548	when the readyness condition is no longer valid even when employing
		549	typical ways of handling events, so its a good idea to use non-blocking
		550	I/O unconditionally.
		551
443	=back	552	=back
444		553
445	=head2 C<ev_timer> - relative and optionally recurring timeouts	554	=head2 C<ev_timer> - relative and optionally recurring timeouts
446		555
447	Timer watchers are simple relative timers that generate an event after a	556	Timer watchers are simple relative timers that generate an event after a
448	given time, and optionally repeating in regular intervals after that.	557	given time, and optionally repeating in regular intervals after that.
449		558
450	The timers are based on real time, that is, if you register an event that	559	The timers are based on real time, that is, if you register an event that
451	times out after an hour and youreset your system clock to last years	560	times out after an hour and you reset your system clock to last years
452	time, it will still time out after (roughly) and hour. "Roughly" because	561	time, it will still time out after (roughly) and hour. "Roughly" because
453	detecting time jumps is hard, and soem inaccuracies are unavoidable (the	562	detecting time jumps is hard, and some inaccuracies are unavoidable (the
454	monotonic clock option helps a lot here).	563	monotonic clock option helps a lot here).
455		564
456	The relative timeouts are calculated relative to the C<ev_now ()>	565	The relative timeouts are calculated relative to the C<ev_now ()>
457	time. This is usually the right thing as this timestamp refers to the time	566	time. This is usually the right thing as this timestamp refers to the time
458	of the event triggering whatever timeout you are modifying/starting. If	567	of the event triggering whatever timeout you are modifying/starting. If
459	you suspect event processing to be delayed and you need to base the timeout	568	you suspect event processing to be delayed and you I<need> to base the timeout
460	ion the current time, use something like this to adjust for this:	569	on the current time, use something like this to adjust for this:
461		570
462	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);	571	ev_timer_set (&timer, after + ev_now () - ev_time (), 0.);
		572
		573	The callback is guarenteed to be invoked only when its timeout has passed,
		574	but if multiple timers become ready during the same loop iteration then
		575	order of execution is undefined.
463		576
464	=over 4	577	=over 4
465		578
466	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)	579	=item ev_timer_init (ev_timer *, callback, ev_tstamp after, ev_tstamp repeat)
467		580
…		…
473	later, again, and again, until stopped manually.	586	later, again, and again, until stopped manually.
474		587
475	The timer itself will do a best-effort at avoiding drift, that is, if you	588	The timer itself will do a best-effort at avoiding drift, that is, if you
476	configure a timer to trigger every 10 seconds, then it will trigger at	589	configure a timer to trigger every 10 seconds, then it will trigger at
477	exactly 10 second intervals. If, however, your program cannot keep up with	590	exactly 10 second intervals. If, however, your program cannot keep up with
478	the timer (ecause it takes longer than those 10 seconds to do stuff) the	591	the timer (because it takes longer than those 10 seconds to do stuff) the
479	timer will not fire more than once per event loop iteration.	592	timer will not fire more than once per event loop iteration.
480		593
481	=item ev_timer_again (loop)	594	=item ev_timer_again (loop)
482		595
483	This will act as if the timer timed out and restart it again if it is	596	This will act as if the timer timed out and restart it again if it is
…		…
514	again).	627	again).
515		628
516	They can also be used to implement vastly more complex timers, such as	629	They can also be used to implement vastly more complex timers, such as
517	triggering an event on eahc midnight, local time.	630	triggering an event on eahc midnight, local time.
518		631
		632	As with timers, the callback is guarenteed to be invoked only when the
		633	time (C<at>) has been passed, but if multiple periodic timers become ready
		634	during the same loop iteration then order of execution is undefined.
		635
519	=over 4	636	=over 4
520		637
521	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)	638	=item ev_periodic_init (ev_periodic *, callback, ev_tstamp at, ev_tstamp interval, reschedule_cb)
522		639
523	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)	640	=item ev_periodic_set (ev_periodic *, ev_tstamp after, ev_tstamp repeat, reschedule_cb)
524		641
525	Lots of arguments, lets sort it out... There are basically three modes of	642	Lots of arguments, lets sort it out... There are basically three modes of
526	operation, and we will explain them from simplest to complex:	643	operation, and we will explain them from simplest to complex:
527
528		644
529	=over 4	645	=over 4
530		646
531	=item * absolute timer (interval = reschedule_cb = 0)	647	=item * absolute timer (interval = reschedule_cb = 0)
532		648
…		…
560	In this mode the values for C<interval> and C<at> are both being	676	In this mode the values for C<interval> and C<at> are both being
561	ignored. Instead, each time the periodic watcher gets scheduled, the	677	ignored. Instead, each time the periodic watcher gets scheduled, the
562	reschedule callback will be called with the watcher as first, and the	678	reschedule callback will be called with the watcher as first, and the
563	current time as second argument.	679	current time as second argument.
564		680
565	NOTE: I<This callback MUST NOT stop or destroy the periodic or any other	681	NOTE: I<This callback MUST NOT stop or destroy any periodic watcher,
566	periodic watcher, ever, or make any event loop modifications>. If you need	682	ever, or make any event loop modifications>. If you need to stop it,
567	to stop it, return C<now + 1e30> (or so, fudge fudge) and stop it afterwards.	683	return C<now + 1e30> (or so, fudge fudge) and stop it afterwards (e.g. by
568		684	starting a prepare watcher).
569	Also, I<< this callback must always return a time that is later than the
570	passed C<now> value >>. Not even C<now> itself will be ok.
571		685
572	Its prototype is C<ev_tstamp (reschedule_cb)(struct ev_periodic w,	686	Its prototype is C<ev_tstamp (reschedule_cb)(struct ev_periodic w,
573	ev_tstamp now)>, e.g.:	687	ev_tstamp now)>, e.g.:
574		688
575	static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)	689	static ev_tstamp my_rescheduler (struct ev_periodic *w, ev_tstamp now)
…		…
580	It must return the next time to trigger, based on the passed time value	694	It must return the next time to trigger, based on the passed time value
581	(that is, the lowest time value larger than to the second argument). It	695	(that is, the lowest time value larger than to the second argument). It
582	will usually be called just before the callback will be triggered, but	696	will usually be called just before the callback will be triggered, but
583	might be called at other times, too.	697	might be called at other times, too.
584		698
		699	NOTE: I<< This callback must always return a time that is later than the
		700	passed C<now> value >>. Not even C<now> itself will do, it I<must> be larger.
		701
585	This can be used to create very complex timers, such as a timer that	702	This can be used to create very complex timers, such as a timer that
586	triggers on each midnight, local time. To do this, you would calculate the	703	triggers on each midnight, local time. To do this, you would calculate the
587	next midnight after C<now> and return the timestamp value for this. How you do this	704	next midnight after C<now> and return the timestamp value for this. How
588	is, again, up to you (but it is not trivial).	705	you do this is, again, up to you (but it is not trivial, which is the main
		706	reason I omitted it as an example).
589		707
590	=back	708	=back
591		709
592	=item ev_periodic_again (loop, ev_periodic *)	710	=item ev_periodic_again (loop, ev_periodic *)
593		711
…		…
672	=back	790	=back
673		791
674	=head2 C<ev_prepare> and C<ev_check> - customise your event loop	792	=head2 C<ev_prepare> and C<ev_check> - customise your event loop
675		793
676	Prepare and check watchers are usually (but not always) used in tandem:	794	Prepare and check watchers are usually (but not always) used in tandem:
677	Prepare watchers get invoked before the process blocks and check watchers	795	prepare watchers get invoked before the process blocks and check watchers
678	afterwards.	796	afterwards.
679		797
680	Their main purpose is to integrate other event mechanisms into libev. This	798	Their main purpose is to integrate other event mechanisms into libev. This
681	could be used, for example, to track variable changes, implement your own	799	could be used, for example, to track variable changes, implement your own
682	watchers, integrate net-snmp or a coroutine library and lots more.	800	watchers, integrate net-snmp or a coroutine library and lots more.
…		…
685	to be watched by the other library, registering C<ev_io> watchers for	803	to be watched by the other library, registering C<ev_io> watchers for
686	them and starting an C<ev_timer> watcher for any timeouts (many libraries	804	them and starting an C<ev_timer> watcher for any timeouts (many libraries
687	provide just this functionality). Then, in the check watcher you check for	805	provide just this functionality). Then, in the check watcher you check for
688	any events that occured (by checking the pending status of all watchers	806	any events that occured (by checking the pending status of all watchers
689	and stopping them) and call back into the library. The I/O and timer	807	and stopping them) and call back into the library. The I/O and timer
690	callbacks will never actually be called (but must be valid neverthelles,	808	callbacks will never actually be called (but must be valid nevertheless,
691	because you never know, you know?).	809	because you never know, you know?).
692		810
693	As another example, the Perl Coro module uses these hooks to integrate	811	As another example, the Perl Coro module uses these hooks to integrate
694	coroutines into libev programs, by yielding to other active coroutines	812	coroutines into libev programs, by yielding to other active coroutines
695	during each prepare and only letting the process block if no coroutines	813	during each prepare and only letting the process block if no coroutines
696	are ready to run (its actually more complicated, it only runs coroutines	814	are ready to run (it's actually more complicated: it only runs coroutines
697	with priority higher than the event loop and one lower priority once,	815	with priority higher than or equal to the event loop and one coroutine
698	using idle watchers to keep the event loop from blocking if lower-priority	816	of lower priority, but only once, using idle watchers to keep the event
699	coroutines exist, thus mapping low-priority coroutines to idle/background	817	loop from blocking if lower-priority coroutines are active, thus mapping
700	tasks).	818	low-priority coroutines to idle/background tasks).
701		819
702	=over 4	820	=over 4
703		821
704	=item ev_prepare_init (ev_prepare *, callback)	822	=item ev_prepare_init (ev_prepare *, callback)
705		823
…		…
720	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)	838	=item ev_once (loop, int fd, int events, ev_tstamp timeout, callback)
721		839
722	This function combines a simple timer and an I/O watcher, calls your	840	This function combines a simple timer and an I/O watcher, calls your
723	callback on whichever event happens first and automatically stop both	841	callback on whichever event happens first and automatically stop both
724	watchers. This is useful if you want to wait for a single event on an fd	842	watchers. This is useful if you want to wait for a single event on an fd
725	or timeout without havign to allocate/configure/start/stop/free one or	843	or timeout without having to allocate/configure/start/stop/free one or
726	more watchers yourself.	844	more watchers yourself.
727		845
728	If C<fd> is less than 0, then no I/O watcher will be started and events	846	If C<fd> is less than 0, then no I/O watcher will be started and events
729	is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and	847	is being ignored. Otherwise, an C<ev_io> watcher for the given C<fd> and
730	C<events> set will be craeted and started.	848	C<events> set will be craeted and started.
…		…
733	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and	851	started. Otherwise an C<ev_timer> watcher with after = C<timeout> (and
734	repeat = 0) will be started. While C<0> is a valid timeout, it is of	852	repeat = 0) will be started. While C<0> is a valid timeout, it is of
735	dubious value.	853	dubious value.
736		854
737	The callback has the type C<void (cb)(int revents, void arg)> and gets	855	The callback has the type C<void (cb)(int revents, void arg)> and gets
738	passed an events set like normal event callbacks (with a combination of	856	passed an C<revents> set like normal event callbacks (a combination of
739	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>	857	C<EV_ERROR>, C<EV_READ>, C<EV_WRITE> or C<EV_TIMEOUT>) and the C<arg>
740	value passed to C<ev_once>:	858	value passed to C<ev_once>:
741		859
742	static void stdin_ready (int revents, void *arg)	860	static void stdin_ready (int revents, void *arg)
743	{	861	{
…		…
764		882
765	Feed an event as if the given signal occured (loop must be the default loop!).	883	Feed an event as if the given signal occured (loop must be the default loop!).
766		884
767	=back	885	=back
768		886
		887	=head1 LIBEVENT EMULATION
		888
		889	Libev offers a compatibility emulation layer for libevent. It cannot
		890	emulate the internals of libevent, so here are some usage hints:
		891
		892	=over 4
		893
		894	=item * Use it by including <event.h>, as usual.
		895
		896	=item * The following members are fully supported: ev_base, ev_callback,
		897	ev_arg, ev_fd, ev_res, ev_events.
		898
		899	=item * Avoid using ev_flags and the EVLIST_*-macros, while it is
		900	maintained by libev, it does not work exactly the same way as in libevent (consider
		901	it a private API).
		902
		903	=item * Priorities are not currently supported. Initialising priorities
		904	will fail and all watchers will have the same priority, even though there
		905	is an ev_pri field.
		906
		907	=item * Other members are not supported.
		908
		909	=item * The libev emulation is I<not> ABI compatible to libevent, you need
		910	to use the libev header file and library.
		911
		912	=back
		913
		914	=head1 C++ SUPPORT
		915
		916	TBD.
		917
769	=head1 AUTHOR	918	=head1 AUTHOR
770		919
771	Marc Lehmann <libev@schmorp.de>.	920	Marc Lehmann <libev@schmorp.de>.
772		921

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.17 by root, Mon Nov 12 08:57:03 2007 UTC vs. Revision 1.32 by root, Fri Nov 23 08:36:35 2007 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.17 by root, Mon Nov 12 08:57:03 2007 UTC vs.
Revision 1.32 by root, Fri Nov 23 08:36:35 2007 UTC