[ViewVC] Diff of: cvs/Coro/Coro.pm

Comparing Coro/Coro.pm (file contents):
Revision 1.234 by root, Fri Nov 21 06:52:10 2008 UTC vs.
Revision 1.274 by root, Sat Dec 12 01:30:26 2009 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	Coro - the real perl threads	3	Coro - the only real threads in perl
4		4
5	=head1 SYNOPSIS	5	=head1 SYNOPSIS
6		6
7	use Coro;	7	use Coro;
8		8
11	print "2\n";	11	print "2\n";
12	cede; # yield back to main	12	cede; # yield back to main
13	print "4\n";	13	print "4\n";
14	};	14	};
15	print "1\n";	15	print "1\n";
16	cede; # yield to coroutine	16	cede; # yield to coro
17	print "3\n";	17	print "3\n";
18	cede; # and again	18	cede; # and again
19		19
20	# use locking	20	# use locking
21	use Coro::Semaphore;	21	use Coro::Semaphore;
…		…
26	$locked = 1;	26	$locked = 1;
27	$lock->up;	27	$lock->up;
28		28
29	=head1 DESCRIPTION	29	=head1 DESCRIPTION
30		30
31	This module collection manages coroutines, that is, cooperative	31	For a tutorial-style introduction, please read the L<Coro::Intro>
32	threads. Coroutines are similar to kernel threads but don't (in general)	32	manpage. This manpage mainly contains reference information.
		33
		34	This module collection manages continuations in general, most often in
		35	the form of cooperative threads (also called coros, or simply "coro"
		36	in the documentation). They are similar to kernel threads but don't (in
33	run in parallel at the same time even on SMP machines. The specific flavor	37	general) run in parallel at the same time even on SMP machines. The
34	of coroutine used in this module also guarantees you that it will not	38	specific flavor of thread offered by this module also guarantees you that
35	switch between coroutines unless necessary, at easily-identified points	39	it will not switch between threads unless necessary, at easily-identified
36	in your program, so locking and parallel access are rarely an issue,	40	points in your program, so locking and parallel access are rarely an
37	making coroutine programming much safer and easier than using other thread	41	issue, making thread programming much safer and easier than using other
38	models.	42	thread models.
39		43
40	Unlike the so-called "Perl threads" (which are not actually real threads	44	Unlike the so-called "Perl threads" (which are not actually real threads
41	but only the windows process emulation ported to unix), Coro provides a	45	but only the windows process emulation (see section of same name for more
		46	details) ported to unix, and as such act as processes), Coro provides
42	full shared address space, which makes communication between coroutines	47	a full shared address space, which makes communication between threads
43	very easy. And coroutines are fast, too: disabling the Windows process	48	very easy. And Coro's threads are fast, too: disabling the Windows
44	emulation code in your perl and using Coro can easily result in a two to	49	process emulation code in your perl and using Coro can easily result in
45	four times speed increase for your programs.	50	a two to four times speed increase for your programs. A parallel matrix
		51	multiplication benchmark runs over 300 times faster on a single core than
		52	perl's pseudo-threads on a quad core using all four cores.
46		53
47	Coro achieves that by supporting multiple running interpreters that share	54	Coro achieves that by supporting multiple running interpreters that share
48	data, which is especially useful to code pseudo-parallel processes and	55	data, which is especially useful to code pseudo-parallel processes and
49	for event-based programming, such as multiple HTTP-GET requests running	56	for event-based programming, such as multiple HTTP-GET requests running
50	concurrently. See L<Coro::AnyEvent> to learn more on how to integrate Coro	57	concurrently. See L<Coro::AnyEvent> to learn more on how to integrate Coro
51	into an event-based environment.	58	into an event-based environment.
52		59
53	In this module, a coroutines is defined as "callchain + lexical variables	60	In this module, a thread is defined as "callchain + lexical variables +
54	+ @_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own	61	some package variables + C stack), that is, a thread has its own callchain,
55	callchain, its own set of lexicals and its own set of perls most important	62	its own set of lexicals and its own set of perls most important global
56	global variables (see L<Coro::State> for more configuration and background	63	variables (see L<Coro::State> for more configuration and background info).
57	info).
58		64
59	See also the C<SEE ALSO> section at the end of this document - the Coro	65	See also the C<SEE ALSO> section at the end of this document - the Coro
60	module family is quite large.	66	module family is quite large.
61		67
62	=cut	68	=cut
63		69
64	package Coro;	70	package Coro;
65		71
66	use strict qw(vars subs);	72	use common::sense;
67	no warnings "uninitialized";	73
		74	use Carp ();
		75
		76	use Guard ();
68		77
69	use Coro::State;	78	use Coro::State;
70		79
71	use base qw(Coro::State Exporter);	80	use base qw(Coro::State Exporter);
72		81
73	our $idle; # idle handler	82	our $idle; # idle handler
74	our $main; # main coroutine	83	our $main; # main coro
75	our $current; # current coroutine	84	our $current; # current coro
76		85
77	our $VERSION = "5.0";	86	our $VERSION = 5.21;
78		87
79	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);	88	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait);
80	our %EXPORT_TAGS = (	89	our %EXPORT_TAGS = (
81	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],	90	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
82	);	91	);
83	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));	92	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));
84		93
…		…
86		95
87	=over 4	96	=over 4
88		97
89	=item $Coro::main	98	=item $Coro::main
90		99
91	This variable stores the coroutine object that represents the main	100	This variable stores the Coro object that represents the main
92	program. While you cna C<ready> it and do most other things you can do to	101	program. While you cna C<ready> it and do most other things you can do to
93	coroutines, it is mainly useful to compare again C<$Coro::current>, to see	102	coro, it is mainly useful to compare again C<$Coro::current>, to see
94	whether you are running in the main program or not.	103	whether you are running in the main program or not.
95		104
96	=cut	105	=cut
97		106
98	# $main is now being initialised by Coro::State	107	# $main is now being initialised by Coro::State
99		108
100	=item $Coro::current	109	=item $Coro::current
101		110
102	The coroutine object representing the current coroutine (the last	111	The Coro object representing the current coro (the last
103	coroutine that the Coro scheduler switched to). The initial value is	112	coro that the Coro scheduler switched to). The initial value is
104	C<$Coro::main> (of course).	113	C<$Coro::main> (of course).
105		114
106	This variable is B<strictly> I<read-only>. You can take copies of the	115	This variable is B<strictly> I<read-only>. You can take copies of the
107	value stored in it and use it as any other coroutine object, but you must	116	value stored in it and use it as any other Coro object, but you must
108	not otherwise modify the variable itself.	117	not otherwise modify the variable itself.
109		118
110	=cut	119	=cut
111		120
112	sub current() { $current } # [DEPRECATED]	121	sub current() { $current } # [DEPRECATED]
113		122
114	=item $Coro::idle	123	=item $Coro::idle
115		124
116	This variable is mainly useful to integrate Coro into event loops. It is	125	This variable is mainly useful to integrate Coro into event loops. It is
117	usually better to rely on L<Coro::AnyEvent> or LC<Coro::EV>, as this is	126	usually better to rely on L<Coro::AnyEvent> or L<Coro::EV>, as this is
118	pretty low-level functionality.	127	pretty low-level functionality.
119		128
120	This variable stores a callback that is called whenever the scheduler	129	This variable stores a Coro object that is put into the ready queue when
121	finds no ready coroutines to run. The default implementation prints	130	there are no other ready threads (without invoking any ready hooks).
122	"FATAL: deadlock detected" and exits, because the program has no other way
123	to continue.
124		131
		132	The default implementation dies with "FATAL: deadlock detected.", followed
		133	by a thread listing, because the program has no other way to continue.
		134
125	This hook is overwritten by modules such as C<Coro::Timer> and	135	This hook is overwritten by modules such as C<Coro::EV> and
126	C<Coro::AnyEvent> to wait on an external event that hopefully wake up a	136	C<Coro::AnyEvent> to wait on an external event that hopefully wake up a
127	coroutine so the scheduler can run it.	137	coro so the scheduler can run it.
128		138
129	Note that the callback I<must not>, under any circumstances, block
130	the current coroutine. Normally, this is achieved by having an "idle
131	coroutine" that calls the event loop and then blocks again, and then
132	readying that coroutine in the idle handler.
133
134	See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this	139	See L<Coro::EV> or L<Coro::AnyEvent> for examples of using this technique.
135	technique.
136		140
137	Please note that if your callback recursively invokes perl (e.g. for event
138	handlers), then it must be prepared to be called recursively itself.
139
140	=cut	141	=cut
141		142
142	$idle = sub {	143	$idle = new Coro sub {
143	require Carp;	144	require Coro::Debug;
144	Carp::croak ("FATAL: deadlock detected");	145	die "FATAL: deadlock detected.\n"
		146	. Coro::Debug::ps_listing ();
145	};	147	};
146		148
147	# this coroutine is necessary because a coroutine	149	# this coro is necessary because a coro
148	# cannot destroy itself.	150	# cannot destroy itself.
149	our @destroy;	151	our @destroy;
150	our $manager;	152	our $manager;
151		153
152	$manager = new Coro sub {	154	$manager = new Coro sub {
153	while () {	155	while () {
154	Coro::_cancel shift @destroy	156	Coro::State::cancel shift @destroy
155	while @destroy;	157	while @destroy;
156		158
157	&schedule;	159	&schedule;
158	}	160	}
159	};	161	};
160	$manager->{desc} = "[coro manager]";	162	$manager->{desc} = "[coro manager]";
161	$manager->prio (PRIO_MAX);	163	$manager->prio (PRIO_MAX);
162		164
163	=back	165	=back
164		166
165	=head1 SIMPLE COROUTINE CREATION	167	=head1 SIMPLE CORO CREATION
166		168
167	=over 4	169	=over 4
168		170
169	=item async { ... } [@args...]	171	=item async { ... } [@args...]
170		172
171	Create a new coroutine and return it's coroutine object (usually	173	Create a new coro and return its Coro object (usually
172	unused). The coroutine will be put into the ready queue, so	174	unused). The coro will be put into the ready queue, so
173	it will start running automatically on the next scheduler run.	175	it will start running automatically on the next scheduler run.
174		176
175	The first argument is a codeblock/closure that should be executed in the	177	The first argument is a codeblock/closure that should be executed in the
176	coroutine. When it returns argument returns the coroutine is automatically	178	coro. When it returns argument returns the coro is automatically
177	terminated.	179	terminated.
178		180
179	The remaining arguments are passed as arguments to the closure.	181	The remaining arguments are passed as arguments to the closure.
180		182
181	See the C<Coro::State::new> constructor for info about the coroutine	183	See the C<Coro::State::new> constructor for info about the coro
182	environment in which coroutines are executed.	184	environment in which coro are executed.
183		185
184	Calling C<exit> in a coroutine will do the same as calling exit outside	186	Calling C<exit> in a coro will do the same as calling exit outside
185	the coroutine. Likewise, when the coroutine dies, the program will exit,	187	the coro. Likewise, when the coro dies, the program will exit,
186	just as it would in the main program.	188	just as it would in the main program.
187		189
188	If you do not want that, you can provide a default C<die> handler, or	190	If you do not want that, you can provide a default C<die> handler, or
189	simply avoid dieing (by use of C<eval>).	191	simply avoid dieing (by use of C<eval>).
190		192
191	Example: Create a new coroutine that just prints its arguments.	193	Example: Create a new coro that just prints its arguments.
192		194
193	async {	195	async {
194	print "@_\n";	196	print "@_\n";
195	} 1,2,3,4;	197	} 1,2,3,4;
196		198
197	=cut
198
199	sub async(&@) {
200	my $coro = new Coro @_;
201	$coro->ready;
202	$coro
203	}
204
205	=item async_pool { ... } [@args...]	199	=item async_pool { ... } [@args...]
206		200
207	Similar to C<async>, but uses a coroutine pool, so you should not call	201	Similar to C<async>, but uses a coro pool, so you should not call
208	terminate or join on it (although you are allowed to), and you get a	202	terminate or join on it (although you are allowed to), and you get a
209	coroutine that might have executed other code already (which can be good	203	coro that might have executed other code already (which can be good
210	or bad :).	204	or bad :).
211		205
212	On the plus side, this function is about twice as fast as creating (and	206	On the plus side, this function is about twice as fast as creating (and
213	destroying) a completely new coroutine, so if you need a lot of generic	207	destroying) a completely new coro, so if you need a lot of generic
214	coroutines in quick successsion, use C<async_pool>, not C<async>.	208	coros in quick successsion, use C<async_pool>, not C<async>.
215		209
216	The code block is executed in an C<eval> context and a warning will be	210	The code block is executed in an C<eval> context and a warning will be
217	issued in case of an exception instead of terminating the program, as	211	issued in case of an exception instead of terminating the program, as
218	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>	212	C<async> does. As the coro is being reused, stuff like C<on_destroy>
219	will not work in the expected way, unless you call terminate or cancel,	213	will not work in the expected way, unless you call terminate or cancel,
220	which somehow defeats the purpose of pooling (but is fine in the	214	which somehow defeats the purpose of pooling (but is fine in the
221	exceptional case).	215	exceptional case).
222		216
223	The priority will be reset to C<0> after each run, tracing will be	217	The priority will be reset to C<0> after each run, tracing will be
224	disabled, the description will be reset and the default output filehandle	218	disabled, the description will be reset and the default output filehandle
225	gets restored, so you can change all these. Otherwise the coroutine will	219	gets restored, so you can change all these. Otherwise the coro will
226	be re-used "as-is": most notably if you change other per-coroutine global	220	be re-used "as-is": most notably if you change other per-coro global
227	stuff such as C<$/> you I<must needs> revert that change, which is most	221	stuff such as C<$/> you I<must needs> revert that change, which is most
228	simply done by using local as in: C<< local $/ >>.	222	simply done by using local as in: C<< local $/ >>.
229		223
230	The idle pool size is limited to C<8> idle coroutines (this can be	224	The idle pool size is limited to C<8> idle coros (this can be
231	adjusted by changing $Coro::POOL_SIZE), but there can be as many non-idle	225	adjusted by changing $Coro::POOL_SIZE), but there can be as many non-idle
232	coros as required.	226	coros as required.
233		227
234	If you are concerned about pooled coroutines growing a lot because a	228	If you are concerned about pooled coros growing a lot because a
235	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool	229	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
236	{ terminate }> once per second or so to slowly replenish the pool. In	230	{ terminate }> once per second or so to slowly replenish the pool. In
237	addition to that, when the stacks used by a handler grows larger than 32kb	231	addition to that, when the stacks used by a handler grows larger than 32kb
238	(adjustable via $Coro::POOL_RSS) it will also be destroyed.	232	(adjustable via $Coro::POOL_RSS) it will also be destroyed.
239		233
…		…
256	=back	250	=back
257		251
258	=head1 STATIC METHODS	252	=head1 STATIC METHODS
259		253
260	Static methods are actually functions that implicitly operate on the	254	Static methods are actually functions that implicitly operate on the
261	current coroutine.	255	current coro.
262		256
263	=over 4	257	=over 4
264		258
265	=item schedule	259	=item schedule
266		260
267	Calls the scheduler. The scheduler will find the next coroutine that is	261	Calls the scheduler. The scheduler will find the next coro that is
268	to be run from the ready queue and switches to it. The next coroutine	262	to be run from the ready queue and switches to it. The next coro
269	to be run is simply the one with the highest priority that is longest	263	to be run is simply the one with the highest priority that is longest
270	in its ready queue. If there is no coroutine ready, it will clal the	264	in its ready queue. If there is no coro ready, it will call the
271	C<$Coro::idle> hook.	265	C<$Coro::idle> hook.
272		266
273	Please note that the current coroutine will I<not> be put into the ready	267	Please note that the current coro will I<not> be put into the ready
274	queue, so calling this function usually means you will never be called	268	queue, so calling this function usually means you will never be called
275	again unless something else (e.g. an event handler) calls C<< ->ready >>,	269	again unless something else (e.g. an event handler) calls C<< ->ready >>,
276	thus waking you up.	270	thus waking you up.
277		271
278	This makes C<schedule> I<the> generic method to use to block the current	272	This makes C<schedule> I<the> generic method to use to block the current
279	coroutine and wait for events: first you remember the current coroutine in	273	coro and wait for events: first you remember the current coro in
280	a variable, then arrange for some callback of yours to call C<< ->ready	274	a variable, then arrange for some callback of yours to call C<< ->ready
281	>> on that once some event happens, and last you call C<schedule> to put	275	>> on that once some event happens, and last you call C<schedule> to put
282	yourself to sleep. Note that a lot of things can wake your coroutine up,	276	yourself to sleep. Note that a lot of things can wake your coro up,
283	so you need to check whether the event indeed happened, e.g. by storing the	277	so you need to check whether the event indeed happened, e.g. by storing the
284	status in a variable.	278	status in a variable.
285		279
286	See B<HOW TO WAIT FOR A CALLBACK>, below, for some ways to wait for callbacks.	280	See B<HOW TO WAIT FOR A CALLBACK>, below, for some ways to wait for callbacks.
287		281
288	=item cede	282	=item cede
289		283
290	"Cede" to other coroutines. This function puts the current coroutine into	284	"Cede" to other coros. This function puts the current coro into
291	the ready queue and calls C<schedule>, which has the effect of giving	285	the ready queue and calls C<schedule>, which has the effect of giving
292	up the current "timeslice" to other coroutines of the same or higher	286	up the current "timeslice" to other coros of the same or higher
293	priority. Once your coroutine gets its turn again it will automatically be	287	priority. Once your coro gets its turn again it will automatically be
294	resumed.	288	resumed.
295		289
296	This function is often called C<yield> in other languages.	290	This function is often called C<yield> in other languages.
297		291
298	=item Coro::cede_notself	292	=item Coro::cede_notself
299		293
300	Works like cede, but is not exported by default and will cede to I<any>	294	Works like cede, but is not exported by default and will cede to I<any>
301	coroutine, regardless of priority. This is useful sometimes to ensure	295	coro, regardless of priority. This is useful sometimes to ensure
302	progress is made.	296	progress is made.
303		297
304	=item terminate [arg...]	298	=item terminate [arg...]
305		299
306	Terminates the current coroutine with the given status values (see L<cancel>).	300	Terminates the current coro with the given status values (see L<cancel>).
		301
		302	=item Coro::on_enter BLOCK, Coro::on_leave BLOCK
		303
		304	These function install enter and leave winders in the current scope. The
		305	enter block will be executed when on_enter is called and whenever the
		306	current coro is re-entered by the scheduler, while the leave block is
		307	executed whenever the current coro is blocked by the scheduler, and
		308	also when the containing scope is exited (by whatever means, be it exit,
		309	die, last etc.).
		310
		311	I<Neither invoking the scheduler, nor exceptions, are allowed within those
		312	BLOCKs>. That means: do not even think about calling C<die> without an
		313	eval, and do not even think of entering the scheduler in any way.
		314
		315	Since both BLOCKs are tied to the current scope, they will automatically
		316	be removed when the current scope exits.
		317
		318	These functions implement the same concept as C<dynamic-wind> in scheme
		319	does, and are useful when you want to localise some resource to a specific
		320	coro.
		321
		322	They slow down thread switching considerably for coros that use them
		323	(about 40% for a BLOCK with a single assignment, so thread switching is
		324	still reasonably fast if the handlers are fast).
		325
		326	These functions are best understood by an example: The following function
		327	will change the current timezone to "Antarctica/South_Pole", which
		328	requires a call to C<tzset>, but by using C<on_enter> and C<on_leave>,
		329	which remember/change the current timezone and restore the previous
		330	value, respectively, the timezone is only changed for the coro that
		331	installed those handlers.
		332
		333	use POSIX qw(tzset);
		334
		335	async {
		336	my $old_tz; # store outside TZ value here
		337
		338	Coro::on_enter {
		339	$old_tz = $ENV{TZ}; # remember the old value
		340
		341	$ENV{TZ} = "Antarctica/South_Pole";
		342	tzset; # enable new value
		343	};
		344
		345	Coro::on_leave {
		346	$ENV{TZ} = $old_tz;
		347	tzset; # restore old value
		348	};
		349
		350	# at this place, the timezone is Antarctica/South_Pole,
		351	# without disturbing the TZ of any other coro.
		352	};
		353
		354	This can be used to localise about any resource (locale, uid, current
		355	working directory etc.) to a block, despite the existance of other
		356	coros.
		357
		358	Another interesting example implements time-sliced multitasking using
		359	interval timers (this could obviously be optimised, but does the job):
		360
		361	# "timeslice" the given block
		362	sub timeslice(&) {
		363	use Time::HiRes ();
		364
		365	Coro::on_enter {
		366	# on entering the thread, we set an VTALRM handler to cede
		367	$SIG{VTALRM} = sub { cede };
		368	# and then start the interval timer
		369	Time::HiRes::setitimer &Time::HiRes::ITIMER_VIRTUAL, 0.01, 0.01;
		370	};
		371	Coro::on_leave {
		372	# on leaving the thread, we stop the interval timer again
		373	Time::HiRes::setitimer &Time::HiRes::ITIMER_VIRTUAL, 0, 0;
		374	};
		375
		376	&{+shift};
		377	}
		378
		379	# use like this:
		380	timeslice {
		381	# The following is an endless loop that would normally
		382	# monopolise the process. Since it runs in a timesliced
		383	# environment, it will regularly cede to other threads.
		384	while () { }
		385	};
		386
307		387
308	=item killall	388	=item killall
309		389
310	Kills/terminates/cancels all coroutines except the currently running	390	Kills/terminates/cancels all coros except the currently running one.
311	one. This is useful after a fork, either in the child or the parent, as
312	usually only one of them should inherit the running coroutines.
313		391
314	Note that while this will try to free some of the main programs resources,	392	Note that while this will try to free some of the main interpreter
		393	resources if the calling coro isn't the main coro, but one
315	you cannot free all of them, so if a coroutine that is not the main	394	cannot free all of them, so if a coro that is not the main coro
316	program calls this function, there will be some one-time resource leak.	395	calls this function, there will be some one-time resource leak.
317		396
318	=cut	397	=cut
319		398
320	sub killall {	399	sub killall {
321	for (Coro::State::list) {	400	for (Coro::State::list) {
…		…
324	}	403	}
325	}	404	}
326		405
327	=back	406	=back
328		407
329	=head1 COROUTINE OBJECT METHODS	408	=head1 CORO OBJECT METHODS
330		409
331	These are the methods you can call on coroutine objects (or to create	410	These are the methods you can call on coro objects (or to create
332	them).	411	them).
333		412
334	=over 4	413	=over 4
335		414
336	=item new Coro \&sub [, @args...]	415	=item new Coro \&sub [, @args...]
337		416
338	Create a new coroutine and return it. When the sub returns, the coroutine	417	Create a new coro and return it. When the sub returns, the coro
339	automatically terminates as if C<terminate> with the returned values were	418	automatically terminates as if C<terminate> with the returned values were
340	called. To make the coroutine run you must first put it into the ready	419	called. To make the coro run you must first put it into the ready
341	queue by calling the ready method.	420	queue by calling the ready method.
342		421
343	See C<async> and C<Coro::State::new> for additional info about the	422	See C<async> and C<Coro::State::new> for additional info about the
344	coroutine environment.	423	coro environment.
345		424
346	=cut	425	=cut
347		426
348	sub _terminate {	427	sub _coro_run {
349	terminate &{+shift};	428	terminate &{+shift};
350	}	429	}
351		430
352	=item $success = $coroutine->ready	431	=item $success = $coro->ready
353		432
354	Put the given coroutine into the end of its ready queue (there is one	433	Put the given coro into the end of its ready queue (there is one
355	queue for each priority) and return true. If the coroutine is already in	434	queue for each priority) and return true. If the coro is already in
356	the ready queue, do nothing and return false.	435	the ready queue, do nothing and return false.
357		436
358	This ensures that the scheduler will resume this coroutine automatically	437	This ensures that the scheduler will resume this coro automatically
359	once all the coroutines of higher priority and all coroutines of the same	438	once all the coro of higher priority and all coro of the same
360	priority that were put into the ready queue earlier have been resumed.	439	priority that were put into the ready queue earlier have been resumed.
361		440
		441	=item $coro->suspend
		442
		443	Suspends the specified coro. A suspended coro works just like any other
		444	coro, except that the scheduler will not select a suspended coro for
		445	execution.
		446
		447	Suspending a coro can be useful when you want to keep the coro from
		448	running, but you don't want to destroy it, or when you want to temporarily
		449	freeze a coro (e.g. for debugging) to resume it later.
		450
		451	A scenario for the former would be to suspend all (other) coros after a
		452	fork and keep them alive, so their destructors aren't called, but new
		453	coros can be created.
		454
		455	=item $coro->resume
		456
		457	If the specified coro was suspended, it will be resumed. Note that when
		458	the coro was in the ready queue when it was suspended, it might have been
		459	unreadied by the scheduler, so an activation might have been lost.
		460
		461	To avoid this, it is best to put a suspended coro into the ready queue
		462	unconditionally, as every synchronisation mechanism must protect itself
		463	against spurious wakeups, and the one in the Coro family certainly do
		464	that.
		465
362	=item $is_ready = $coroutine->is_ready	466	=item $is_ready = $coro->is_ready
363		467
364	Return whether the coroutine is currently the ready queue or not,	468	Returns true iff the Coro object is in the ready queue. Unless the Coro
		469	object gets destroyed, it will eventually be scheduled by the scheduler.
365		470
		471	=item $is_running = $coro->is_running
		472
		473	Returns true iff the Coro object is currently running. Only one Coro object
		474	can ever be in the running state (but it currently is possible to have
		475	multiple running Coro::States).
		476
		477	=item $is_suspended = $coro->is_suspended
		478
		479	Returns true iff this Coro object has been suspended. Suspended Coros will
		480	not ever be scheduled.
		481
366	=item $coroutine->cancel (arg...)	482	=item $coro->cancel (arg...)
367		483
368	Terminates the given coroutine and makes it return the given arguments as	484	Terminates the given Coro and makes it return the given arguments as
369	status (default: the empty list). Never returns if the coroutine is the	485	status (default: the empty list). Never returns if the Coro is the
370	current coroutine.	486	current Coro.
371		487
372	=cut	488	=cut
373		489
374	sub cancel {	490	sub cancel {
375	my $self = shift;	491	my $self = shift;
376		492
377	if ($current == $self) {	493	if ($current == $self) {
378	terminate @_;	494	terminate @_;
379	} else {	495	} else {
380	$self->{_status} = [@_];	496	$self->{_status} = [@_];
381	$self->_cancel;	497	Coro::State::cancel $self;
382	}	498	}
383	}	499	}
384		500
385	=item $coroutine->schedule_to	501	=item $coro->schedule_to
386		502
387	Puts the current coroutine to sleep (like C<Coro::schedule>), but instead	503	Puts the current coro to sleep (like C<Coro::schedule>), but instead
388	of continuing with the next coro from the ready queue, always switch to	504	of continuing with the next coro from the ready queue, always switch to
389	the given coroutine object (regardless of priority etc.). The readyness	505	the given coro object (regardless of priority etc.). The readyness
390	state of that coroutine isn't changed.	506	state of that coro isn't changed.
391		507
392	This is an advanced method for special cases - I'd love to hear about any	508	This is an advanced method for special cases - I'd love to hear about any
393	uses for this one.	509	uses for this one.
394		510
395	=item $coroutine->cede_to	511	=item $coro->cede_to
396		512
397	Like C<schedule_to>, but puts the current coroutine into the ready	513	Like C<schedule_to>, but puts the current coro into the ready
398	queue. This has the effect of temporarily switching to the given	514	queue. This has the effect of temporarily switching to the given
399	coroutine, and continuing some time later.	515	coro, and continuing some time later.
400		516
401	This is an advanced method for special cases - I'd love to hear about any	517	This is an advanced method for special cases - I'd love to hear about any
402	uses for this one.	518	uses for this one.
403		519
404	=item $coroutine->throw ([$scalar])	520	=item $coro->throw ([$scalar])
405		521
406	If C<$throw> is specified and defined, it will be thrown as an exception	522	If C<$throw> is specified and defined, it will be thrown as an exception
407	inside the coroutine at the next convenient point in time. Otherwise	523	inside the coro at the next convenient point in time. Otherwise
408	clears the exception object.	524	clears the exception object.
409		525
410	Coro will check for the exception each time a schedule-like-function	526	Coro will check for the exception each time a schedule-like-function
411	returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down	527	returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down
412	>>, C<< Coro::Handle->readable >> and so on. Most of these functions	528	>>, C<< Coro::Handle->readable >> and so on. Most of these functions
…		…
414		530
415	The exception object will be thrown "as is" with the specified scalar in	531	The exception object will be thrown "as is" with the specified scalar in
416	C<$@>, i.e. if it is a string, no line number or newline will be appended	532	C<$@>, i.e. if it is a string, no line number or newline will be appended
417	(unlike with C<die>).	533	(unlike with C<die>).
418		534
419	This can be used as a softer means than C<cancel> to ask a coroutine to	535	This can be used as a softer means than C<cancel> to ask a coro to
420	end itself, although there is no guarantee that the exception will lead to	536	end itself, although there is no guarantee that the exception will lead to
421	termination, and if the exception isn't caught it might well end the whole	537	termination, and if the exception isn't caught it might well end the whole
422	program.	538	program.
423		539
424	You might also think of C<throw> as being the moral equivalent of	540	You might also think of C<throw> as being the moral equivalent of
425	C<kill>ing a coroutine with a signal (in this case, a scalar).	541	C<kill>ing a coro with a signal (in this case, a scalar).
426		542
427	=item $coroutine->join	543	=item $coro->join
428		544
429	Wait until the coroutine terminates and return any values given to the	545	Wait until the coro terminates and return any values given to the
430	C<terminate> or C<cancel> functions. C<join> can be called concurrently	546	C<terminate> or C<cancel> functions. C<join> can be called concurrently
431	from multiple coroutines, and all will be resumed and given the status	547	from multiple coro, and all will be resumed and given the status
432	return once the C<$coroutine> terminates.	548	return once the C<$coro> terminates.
433		549
434	=cut	550	=cut
435		551
436	sub join {	552	sub join {
437	my $self = shift;	553	my $self = shift;
…		…
448	}	564	}
449		565
450	wantarray ? @{$self->{_status}} : $self->{_status}[0];	566	wantarray ? @{$self->{_status}} : $self->{_status}[0];
451	}	567	}
452		568
453	=item $coroutine->on_destroy (\&cb)	569	=item $coro->on_destroy (\&cb)
454		570
455	Registers a callback that is called when this coroutine gets destroyed,	571	Registers a callback that is called when this coro gets destroyed,
456	but before it is joined. The callback gets passed the terminate arguments,	572	but before it is joined. The callback gets passed the terminate arguments,
457	if any, and I<must not> die, under any circumstances.	573	if any, and I<must not> die, under any circumstances.
458		574
459	=cut	575	=cut
460		576
…		…
462	my ($self, $cb) = @_;	578	my ($self, $cb) = @_;
463		579
464	push @{ $self->{_on_destroy} }, $cb;	580	push @{ $self->{_on_destroy} }, $cb;
465	}	581	}
466		582
467	=item $oldprio = $coroutine->prio ($newprio)	583	=item $oldprio = $coro->prio ($newprio)
468		584
469	Sets (or gets, if the argument is missing) the priority of the	585	Sets (or gets, if the argument is missing) the priority of the
470	coroutine. Higher priority coroutines get run before lower priority	586	coro. Higher priority coro get run before lower priority
471	coroutines. Priorities are small signed integers (currently -4 .. +3),	587	coro. Priorities are small signed integers (currently -4 .. +3),
472	that you can refer to using PRIO_xxx constants (use the import tag :prio	588	that you can refer to using PRIO_xxx constants (use the import tag :prio
473	to get then):	589	to get then):
474		590
475	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN	591	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
476	3 > 1 > 0 > -1 > -3 > -4	592	3 > 1 > 0 > -1 > -3 > -4
477		593
478	# set priority to HIGH	594	# set priority to HIGH
479	current->prio(PRIO_HIGH);	595	current->prio (PRIO_HIGH);
480		596
481	The idle coroutine ($Coro::idle) always has a lower priority than any	597	The idle coro ($Coro::idle) always has a lower priority than any
482	existing coroutine.	598	existing coro.
483		599
484	Changing the priority of the current coroutine will take effect immediately,	600	Changing the priority of the current coro will take effect immediately,
485	but changing the priority of coroutines in the ready queue (but not	601	but changing the priority of coro in the ready queue (but not
486	running) will only take effect after the next schedule (of that	602	running) will only take effect after the next schedule (of that
487	coroutine). This is a bug that will be fixed in some future version.	603	coro). This is a bug that will be fixed in some future version.
488		604
489	=item $newprio = $coroutine->nice ($change)	605	=item $newprio = $coro->nice ($change)
490		606
491	Similar to C<prio>, but subtract the given value from the priority (i.e.	607	Similar to C<prio>, but subtract the given value from the priority (i.e.
492	higher values mean lower priority, just as in unix).	608	higher values mean lower priority, just as in unix).
493		609
494	=item $olddesc = $coroutine->desc ($newdesc)	610	=item $olddesc = $coro->desc ($newdesc)
495		611
496	Sets (or gets in case the argument is missing) the description for this	612	Sets (or gets in case the argument is missing) the description for this
497	coroutine. This is just a free-form string you can associate with a	613	coro. This is just a free-form string you can associate with a
498	coroutine.	614	coro.
499		615
500	This method simply sets the C<< $coroutine->{desc} >> member to the given	616	This method simply sets the C<< $coro->{desc} >> member to the given
501	string. You can modify this member directly if you wish.	617	string. You can modify this member directly if you wish.
502		618
503	=cut	619	=cut
504		620
505	sub desc {	621	sub desc {
…		…
519		635
520	=over 4	636	=over 4
521		637
522	=item Coro::nready	638	=item Coro::nready
523		639
524	Returns the number of coroutines that are currently in the ready state,	640	Returns the number of coro that are currently in the ready state,
525	i.e. that can be switched to by calling C<schedule> directory or	641	i.e. that can be switched to by calling C<schedule> directory or
526	indirectly. The value C<0> means that the only runnable coroutine is the	642	indirectly. The value C<0> means that the only runnable coro is the
527	currently running one, so C<cede> would have no effect, and C<schedule>	643	currently running one, so C<cede> would have no effect, and C<schedule>
528	would cause a deadlock unless there is an idle handler that wakes up some	644	would cause a deadlock unless there is an idle handler that wakes up some
529	coroutines.	645	coro.
530		646
531	=item my $guard = Coro::guard { ... }	647	=item my $guard = Coro::guard { ... }
532		648
533	This creates and returns a guard object. Nothing happens until the object	649	This function still exists, but is deprecated. Please use the
534	gets destroyed, in which case the codeblock given as argument will be	650	C<Guard::guard> function instead.
535	executed. This is useful to free locks or other resources in case of a
536	runtime error or when the coroutine gets canceled, as in both cases the
537	guard block will be executed. The guard object supports only one method,
538	C<< ->cancel >>, which will keep the codeblock from being executed.
539		651
540	Example: set some flag and clear it again when the coroutine gets canceled
541	or the function returns:
542
543	sub do_something {
544	my $guard = Coro::guard { $busy = 0 };
545	$busy = 1;
546
547	# do something that requires $busy to be true
548	}
549
550	=cut	652	=cut
551		653
552	sub guard(&) {	654	BEGIN { *guard = \&Guard::guard }
553	bless \(my $cb = $_[0]), "Coro::guard"
554	}
555
556	sub Coro::guard::cancel {
557	${$_[0]} = sub { };
558	}
559
560	sub Coro::guard::DESTROY {
561	${$_[0]}->();
562	}
563
564		655
565	=item unblock_sub { ... }	656	=item unblock_sub { ... }
566		657
567	This utility function takes a BLOCK or code reference and "unblocks" it,	658	This utility function takes a BLOCK or code reference and "unblocks" it,
568	returning a new coderef. Unblocking means that calling the new coderef	659	returning a new coderef. Unblocking means that calling the new coderef
569	will return immediately without blocking, returning nothing, while the	660	will return immediately without blocking, returning nothing, while the
570	original code ref will be called (with parameters) from within another	661	original code ref will be called (with parameters) from within another
571	coroutine.	662	coro.
572		663
573	The reason this function exists is that many event libraries (such as the	664	The reason this function exists is that many event libraries (such as the
574	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form	665	venerable L<Event\|Event> module) are not thread-safe (a weaker form
575	of thread-safety). This means you must not block within event callbacks,	666	of reentrancy). This means you must not block within event callbacks,
576	otherwise you might suffer from crashes or worse. The only event library	667	otherwise you might suffer from crashes or worse. The only event library
577	currently known that is safe to use without C<unblock_sub> is L<EV>.	668	currently known that is safe to use without C<unblock_sub> is L<EV>.
578		669
		670	Coro will try to catch you when you block in the event loop
		671	("FATAL:$Coro::IDLE blocked itself"), but this is just best effort and
		672	only works when you do not run your own event loop.
		673
579	This function allows your callbacks to block by executing them in another	674	This function allows your callbacks to block by executing them in another
580	coroutine where it is safe to block. One example where blocking is handy	675	coro where it is safe to block. One example where blocking is handy
581	is when you use the L<Coro::AIO\|Coro::AIO> functions to save results to	676	is when you use the L<Coro::AIO\|Coro::AIO> functions to save results to
582	disk, for example.	677	disk, for example.
583		678
584	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when	679	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when
585	creating event callbacks that want to block.	680	creating event callbacks that want to block.
586		681
587	If your handler does not plan to block (e.g. simply sends a message to	682	If your handler does not plan to block (e.g. simply sends a message to
588	another coroutine, or puts some other coroutine into the ready queue),	683	another coro, or puts some other coro into the ready queue), there is
589	there is no reason to use C<unblock_sub>.	684	no reason to use C<unblock_sub>.
590		685
591	Note that you also need to use C<unblock_sub> for any other callbacks that	686	Note that you also need to use C<unblock_sub> for any other callbacks that
592	are indirectly executed by any C-based event loop. For example, when you	687	are indirectly executed by any C-based event loop. For example, when you
593	use a module that uses L<AnyEvent> (and you use L<Coro::AnyEvent>) and it	688	use a module that uses L<AnyEvent> (and you use L<Coro::AnyEvent>) and it
594	provides callbacks that are the result of some event callback, then you	689	provides callbacks that are the result of some event callback, then you
…		…
624	unshift @unblock_queue, [$cb, @_];	719	unshift @unblock_queue, [$cb, @_];
625	$unblock_scheduler->ready;	720	$unblock_scheduler->ready;
626	}	721	}
627	}	722	}
628		723
629	=item $cb = Coro::rouse_cb	724	=item $cb = rouse_cb
630		725
631	Create and return a "rouse callback". That's a code reference that, when	726	Create and return a "rouse callback". That's a code reference that,
632	called, will save its arguments and notify the owner coroutine of the	727	when called, will remember a copy of its arguments and notify the owner
633	callback.	728	coro of the callback.
634		729
635	See the next function.	730	See the next function.
636		731
637	=item @args = Coro::rouse_wait [$cb]	732	=item @args = rouse_wait [$cb]
638		733
639	Wait for the specified rouse callback (or the last one tht was created in	734	Wait for the specified rouse callback (or the last one that was created in
640	this coroutine).	735	this coro).
641		736
642	As soon as the callback is invoked (or when the calback was invoked before	737	As soon as the callback is invoked (or when the callback was invoked
643	C<rouse_wait>), it will return a copy of the arguments originally passed	738	before C<rouse_wait>), it will return the arguments originally passed to
644	to the rouse callback.	739	the rouse callback. In scalar context, that means you get the I<last>
		740	argument, just as if C<rouse_wait> had a C<return ($a1, $a2, $a3...)>
		741	statement at the end.
645		742
646	See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example.	743	See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example.
647		744
648	=back	745	=back
649		746
…		…
651		748
652	1;	749	1;
653		750
654	=head1 HOW TO WAIT FOR A CALLBACK	751	=head1 HOW TO WAIT FOR A CALLBACK
655		752
656	It is very common for a coroutine to wait for some callback to be	753	It is very common for a coro to wait for some callback to be
657	called. This occurs naturally when you use coroutines in an otherwise	754	called. This occurs naturally when you use coro in an otherwise
658	event-based program, or when you use event-based libraries.	755	event-based program, or when you use event-based libraries.
659		756
660	These typically register a callback for some event, and call that callback	757	These typically register a callback for some event, and call that callback
661	when the event occured. In a coroutine, however, you typically want to	758	when the event occured. In a coro, however, you typically want to
662	just wait for the event, simplyifying things.	759	just wait for the event, simplyifying things.
663		760
664	For example C<< AnyEvent->child >> registers a callback to be called when	761	For example C<< AnyEvent->child >> registers a callback to be called when
665	a specific child has exited:	762	a specific child has exited:
666		763
667	my $child_watcher = AnyEvent->child (pid => $pid, cb => sub { ... });	764	my $child_watcher = AnyEvent->child (pid => $pid, cb => sub { ... });
668		765
669	But from withina coroutine, you often just want to write this:	766	But from within a coro, you often just want to write this:
670		767
671	my $status = wait_for_child $pid;	768	my $status = wait_for_child $pid;
672		769
673	Coro offers two functions specifically designed to make this easy,	770	Coro offers two functions specifically designed to make this easy,
674	C<Coro::rouse_cb> and C<Coro::rouse_wait>.	771	C<Coro::rouse_cb> and C<Coro::rouse_wait>.
675		772
676	The first function, C<rouse_cb>, generates and returns a callback that,	773	The first function, C<rouse_cb>, generates and returns a callback that,
677	when invoked, will save it's arguments and notify the coroutine that	774	when invoked, will save its arguments and notify the coro that
678	created the callback.	775	created the callback.
679		776
680	The second function, C<rouse_wait>, waits for the callback to be called	777	The second function, C<rouse_wait>, waits for the callback to be called
681	(by calling C<schedule> to go to sleep) and returns the arguments	778	(by calling C<schedule> to go to sleep) and returns the arguments
682	originally passed to the callback.	779	originally passed to the callback.
…		…
697	you can roll your own, using C<schedule>:	794	you can roll your own, using C<schedule>:
698		795
699	sub wait_for_child($) {	796	sub wait_for_child($) {
700	my ($pid) = @_;	797	my ($pid) = @_;
701		798
702	# store the current coroutine in $current,	799	# store the current coro in $current,
703	# and provide result variables for the closure passed to ->child	800	# and provide result variables for the closure passed to ->child
704	my $current = $Coro::current;	801	my $current = $Coro::current;
705	my ($done, $rstatus);	802	my ($done, $rstatus);
706		803
707	# pass a closure to ->child	804	# pass a closure to ->child
…		…
723		820
724	=item fork with pthread backend	821	=item fork with pthread backend
725		822
726	When Coro is compiled using the pthread backend (which isn't recommended	823	When Coro is compiled using the pthread backend (which isn't recommended
727	but required on many BSDs as their libcs are completely broken), then	824	but required on many BSDs as their libcs are completely broken), then
728	coroutines will not survive a fork. There is no known workaround except to	825	coro will not survive a fork. There is no known workaround except to
729	fix your libc and use a saner backend.	826	fix your libc and use a saner backend.
730		827
731	=item perl process emulation ("threads")	828	=item perl process emulation ("threads")
732		829
733	This module is not perl-pseudo-thread-safe. You should only ever use this	830	This module is not perl-pseudo-thread-safe. You should only ever use this
734	module from the same thread (this requirement might be removed in the	831	module from the first thread (this requirement might be removed in the
735	future to allow per-thread schedulers, but Coro::State does not yet allow	832	future to allow per-thread schedulers, but Coro::State does not yet allow
736	this). I recommend disabling thread support and using processes, as having	833	this). I recommend disabling thread support and using processes, as having
737	the windows process emulation enabled under unix roughly halves perl	834	the windows process emulation enabled under unix roughly halves perl
738	performance, even when not used.	835	performance, even when not used.
739		836
740	=item coroutine switching not signal safe	837	=item coro switching is not signal safe
741		838
742	You must not switch to another coroutine from within a signal handler	839	You must not switch to another coro from within a signal handler (only
743	(only relevant with %SIG - most event libraries provide safe signals).	840	relevant with %SIG - most event libraries provide safe signals), I<unless>
		841	you are sure you are not interrupting a Coro function.
744		842
745	That means you I<MUST NOT> call any function that might "block" the	843	That means you I<MUST NOT> call any function that might "block" the
746	current coroutine - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or	844	current coro - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or
747	anything that calls those. Everything else, including calling C<ready>,	845	anything that calls those. Everything else, including calling C<ready>,
748	works.	846	works.
749		847
750	=back	848	=back
751		849
752		850
		851	=head1 WINDOWS PROCESS EMULATION
		852
		853	A great many people seem to be confused about ithreads (for example, Chip
		854	Salzenberg called me unintelligent, incapable, stupid and gullible,
		855	while in the same mail making rather confused statements about perl
		856	ithreads (for example, that memory or files would be shared), showing his
		857	lack of understanding of this area - if it is hard to understand for Chip,
		858	it is probably not obvious to everybody).
		859
		860	What follows is an ultra-condensed version of my talk about threads in
		861	scripting languages given onthe perl workshop 2009:
		862
		863	The so-called "ithreads" were originally implemented for two reasons:
		864	first, to (badly) emulate unix processes on native win32 perls, and
		865	secondly, to replace the older, real thread model ("5.005-threads").
		866
		867	It does that by using threads instead of OS processes. The difference
		868	between processes and threads is that threads share memory (and other
		869	state, such as files) between threads within a single process, while
		870	processes do not share anything (at least not semantically). That
		871	means that modifications done by one thread are seen by others, while
		872	modifications by one process are not seen by other processes.
		873
		874	The "ithreads" work exactly like that: when creating a new ithreads
		875	process, all state is copied (memory is copied physically, files and code
		876	is copied logically). Afterwards, it isolates all modifications. On UNIX,
		877	the same behaviour can be achieved by using operating system processes,
		878	except that UNIX typically uses hardware built into the system to do this
		879	efficiently, while the windows process emulation emulates this hardware in
		880	software (rather efficiently, but of course it is still much slower than
		881	dedicated hardware).
		882
		883	As mentioned before, loading code, modifying code, modifying data
		884	structures and so on is only visible in the ithreads process doing the
		885	modification, not in other ithread processes within the same OS process.
		886
		887	This is why "ithreads" do not implement threads for perl at all, only
		888	processes. What makes it so bad is that on non-windows platforms, you can
		889	actually take advantage of custom hardware for this purpose (as evidenced
		890	by the forks module, which gives you the (i-) threads API, just much
		891	faster).
		892
		893	Sharing data is in the i-threads model is done by transfering data
		894	structures between threads using copying semantics, which is very slow -
		895	shared data simply does not exist. Benchmarks using i-threads which are
		896	communication-intensive show extremely bad behaviour with i-threads (in
		897	fact, so bad that Coro, which cannot take direct advantage of multiple
		898	CPUs, is often orders of magnitude faster because it shares data using
		899	real threads, refer to my talk for details).
		900
		901	As summary, i-threads use threads to implement processes, while
		902	the compatible forks module uses processes to emulate, uhm,
		903	processes. I-threads slow down every perl program when enabled, and
		904	outside of windows, serve no (or little) practical purpose, but
		905	disadvantages every single-threaded Perl program.
		906
		907	This is the reason that I try to avoid the name "ithreads", as it is
		908	misleading as it implies that it implements some kind of thread model for
		909	perl, and prefer the name "windows process emulation", which describes the
		910	actual use and behaviour of it much better.
		911
753	=head1 SEE ALSO	912	=head1 SEE ALSO
754		913
755	Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.	914	Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
756		915
757	Debugging: L<Coro::Debug>.	916	Debugging: L<Coro::Debug>.
758		917
759	Support/Utility: L<Coro::Specific>, L<Coro::Util>.	918	Support/Utility: L<Coro::Specific>, L<Coro::Util>.
760		919
761	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.	920	Locking and IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>,
		921	L<Coro::SemaphoreSet>, L<Coro::RWLock>.
762		922
763	IO/Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>.	923	I/O and Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>.
764		924
765	Compatibility: L<Coro::LWP>, L<Coro::BDB>, L<Coro::Storable>, L<Coro::Select>.	925	Compatibility with other modules: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for
		926	a better-working alternative), L<Coro::BDB>, L<Coro::Storable>,
		927	L<Coro::Select>.
766		928
767	XS API: L<Coro::MakeMaker>.	929	XS API: L<Coro::MakeMaker>.
768		930
769	Low level Configuration, Coroutine Environment: L<Coro::State>.	931	Low level Configuration, Thread Environment, Continuations: L<Coro::State>.
770		932
771	=head1 AUTHOR	933	=head1 AUTHOR
772		934
773	Marc Lehmann <schmorp@schmorp.de>	935	Marc Lehmann <schmorp@schmorp.de>
774	http://home.schmorp.de/	936	http://home.schmorp.de/

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.234 by root, Fri Nov 21 06:52:10 2008 UTC vs. Revision 1.274 by root, Sat Dec 12 01:30:26 2009 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.234 by root, Fri Nov 21 06:52:10 2008 UTC vs.
Revision 1.274 by root, Sat Dec 12 01:30:26 2009 UTC