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

Comparing libev/ev.pod (file contents):
Revision 1.135 by root, Sat Mar 8 10:38:40 2008 UTC vs.
Revision 1.139 by root, Wed Apr 2 05:51:40 2008 UTC

…		…
275	flags. If that is troubling you, check C<ev_backend ()> afterwards).	275	flags. If that is troubling you, check C<ev_backend ()> afterwards).
276		276
277	If you don't know what event loop to use, use the one returned from this	277	If you don't know what event loop to use, use the one returned from this
278	function.	278	function.
279		279
		280	Note that this function is I<not> thread-safe, so if you want to use it
		281	from multiple threads, you have to lock (note also that this is unlikely,
		282	as loops cannot bes hared easily between threads anyway).
		283
280	The default loop is the only loop that can handle C<ev_signal> and	284	The default loop is the only loop that can handle C<ev_signal> and
281	C<ev_child> watchers, and to do this, it always registers a handler	285	C<ev_child> watchers, and to do this, it always registers a handler
282	for C<SIGCHLD>. If this is a problem for your app you can either	286	for C<SIGCHLD>. If this is a problem for your app you can either
283	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you	287	create a dynamic loop with C<ev_loop_new> that doesn't do that, or you
284	can simply overwrite the C<SIGCHLD> signal handler I<after> calling	288	can simply overwrite the C<SIGCHLD> signal handler I<after> calling
…		…
465		469
466	Similar to C<ev_default_loop>, but always creates a new event loop that is	470	Similar to C<ev_default_loop>, but always creates a new event loop that is
467	always distinct from the default loop. Unlike the default loop, it cannot	471	always distinct from the default loop. Unlike the default loop, it cannot
468	handle signal and child watchers, and attempts to do so will be greeted by	472	handle signal and child watchers, and attempts to do so will be greeted by
469	undefined behaviour (or a failed assertion if assertions are enabled).	473	undefined behaviour (or a failed assertion if assertions are enabled).
		474
		475	Note that this function I<is> thread-safe, and the recommended way to use
		476	libev with threads is indeed to create one loop per thread, and using the
		477	default loop in the "main" or "initial" thread.
470		478
471	Example: Try to create a event loop that uses epoll and nothing else.	479	Example: Try to create a event loop that uses epoll and nothing else.
472		480
473	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL \| EVFLAG_NOENV);	481	struct ev_loop *epoller = ev_loop_new (EVBACKEND_EPOLL \| EVFLAG_NOENV);
474	if (!epoller)	482	if (!epoller)
…		…
1085	To support fork in your programs, you either have to call	1093	To support fork in your programs, you either have to call
1086	C<ev_default_fork ()> or C<ev_loop_fork ()> after a fork in the child,	1094	C<ev_default_fork ()> or C<ev_loop_fork ()> after a fork in the child,
1087	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or	1095	enable C<EVFLAG_FORKCHECK>, or resort to C<EVBACKEND_SELECT> or
1088	C<EVBACKEND_POLL>.	1096	C<EVBACKEND_POLL>.
1089		1097
		1098	=head3 The special problem of SIGPIPE
		1099
		1100	While not really specific to libev, it is easy to forget about SIGPIPE:
		1101	when reading from a pipe whose other end has been closed, your program
		1102	gets send a SIGPIPE, which, by default, aborts your program. For most
		1103	programs this is sensible behaviour, for daemons, this is usually
		1104	undesirable.
		1105
		1106	So when you encounter spurious, unexplained daemon exits, make sure you
		1107	ignore SIGPIPE (and maybe make sure you log the exit status of your daemon
		1108	somewhere, as that would have given you a big clue).
		1109
1090		1110
1091	=head3 Watcher-Specific Functions	1111	=head3 Watcher-Specific Functions
1092		1112
1093	=over 4	1113	=over 4
1094		1114
…		…
1599	reader). Inotify will be used to give hints only and should not change the	1619	reader). Inotify will be used to give hints only and should not change the
1600	semantics of C<ev_stat> watchers, which means that libev sometimes needs	1620	semantics of C<ev_stat> watchers, which means that libev sometimes needs
1601	to fall back to regular polling again even with inotify, but changes are	1621	to fall back to regular polling again even with inotify, but changes are
1602	usually detected immediately, and if the file exists there will be no	1622	usually detected immediately, and if the file exists there will be no
1603	polling.	1623	polling.
		1624
		1625	=head3 ABI Issues (Largefile Support)
		1626
		1627	Libev by default (unless the user overrides this) uses the default
		1628	compilation environment, which means that on systems with optionally
		1629	disabled large file support, you get the 32 bit version of the stat
		1630	structure. When using the library from programs that change the ABI to
		1631	use 64 bit file offsets the programs will fail. In that case you have to
		1632	compile libev with the same flags to get binary compatibility. This is
		1633	obviously the case with any flags that change the ABI, but the problem is
		1634	most noticably with ev_stat and largefile support.
1604		1635
1605	=head3 Inotify	1636	=head3 Inotify
1606		1637
1607	When C<inotify (7)> support has been compiled into libev (generally only	1638	When C<inotify (7)> support has been compiled into libev (generally only
1608	available on Linux) and present at runtime, it will be used to speed up	1639	available on Linux) and present at runtime, it will be used to speed up
…		…
2509	io.start (fd, ev::READ);	2540	io.start (fd, ev::READ);
2510	}	2541	}
2511	};	2542	};
2512		2543
2513		2544
		2545	=head1 OTHER LANGUAGE BINDINGS
		2546
		2547	Libev does not offer other language bindings itself, but bindings for a
		2548	numbe rof languages exist in the form of third-party packages. If you know
		2549	any interesting language binding in addition to the ones listed here, drop
		2550	me a note.
		2551
		2552	=over 4
		2553
		2554	=item Perl
		2555
		2556	The EV module implements the full libev API and is actually used to test
		2557	libev. EV is developed together with libev. Apart from the EV core module,
		2558	there are additional modules that implement libev-compatible interfaces
		2559	to C<libadns> (C<EV::ADNS>), C<Net::SNMP> (C<Net::SNMP::EV>) and the
		2560	C<libglib> event core (C<Glib::EV> and C<EV::Glib>).
		2561
		2562	It can be found and installed via CPAN, its homepage is found at
		2563	L<http://software.schmorp.de/pkg/EV>.
		2564
		2565	=item Ruby
		2566
		2567	Tony Arcieri has written a ruby extension that offers access to a subset
		2568	of the libev API and adds filehandle abstractions, asynchronous DNS and
		2569	more on top of it. It can be found via gem servers. Its homepage is at
		2570	L<http://rev.rubyforge.org/>.
		2571
		2572	=item D
		2573
		2574	Leandro Lucarella has written a D language binding (F<ev.d>) for libev, to
		2575	be found at L<http://git.llucax.com.ar/?p=software/ev.d.git;a=summary>.
		2576
		2577	=back
		2578
		2579
2514	=head1 MACRO MAGIC	2580	=head1 MACRO MAGIC
2515		2581
2516	Libev can be compiled with a variety of options, the most fundamantal	2582	Libev can be compiled with a variety of options, the most fundamantal
2517	of which is C<EV_MULTIPLICITY>. This option determines whether (most)	2583	of which is C<EV_MULTIPLICITY>. This option determines whether (most)
2518	functions and callbacks have an initial C<struct ev_loop *> argument.	2584	functions and callbacks have an initial C<struct ev_loop *> argument.

Diff Legend

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

Comparing libev/ev.pod (file contents): Revision 1.135 by root, Sat Mar 8 10:38:40 2008 UTC vs. Revision 1.139 by root, Wed Apr 2 05:51:40 2008 UTC

Diff Legend

Comparing libev/ev.pod (file contents):
Revision 1.135 by root, Sat Mar 8 10:38:40 2008 UTC vs.
Revision 1.139 by root, Wed Apr 2 05:51:40 2008 UTC