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

Comparing Coro/Coro.pm (file contents):
Revision 1.237 by root, Sat Nov 22 16:37:11 2008 UTC vs.
Revision 1.346 by root, Fri Jul 14 23:20:07 2017 UTC

…		…
1	=head1 NAME	1	=head1 NAME
2		2
3	Coro - real threads in perl	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;
22	my $lock = new Coro::Semaphore;	21	my $lock = new Coro::Semaphore;
23	my $locked;	22	my $locked;
24		23
25	$lock->down;	24	$lock->down;
26	$locked = 1;	25	$locked = 1;
…		…
29	=head1 DESCRIPTION	28	=head1 DESCRIPTION
30		29
31	For a tutorial-style introduction, please read the L<Coro::Intro>	30	For a tutorial-style introduction, please read the L<Coro::Intro>
32	manpage. This manpage mainly contains reference information.	31	manpage. This manpage mainly contains reference information.
33		32
34	This module collection manages coroutines, that is, cooperative	33	This module collection manages continuations in general, most often in
35	threads. Coroutines are similar to kernel threads but don't (in general)	34	the form of cooperative threads (also called coros, or simply "coro"
		35	in the documentation). They are similar to kernel threads but don't (in
36	run in parallel at the same time even on SMP machines. The specific flavor	36	general) run in parallel at the same time even on SMP machines. The
37	of coroutine used in this module also guarantees you that it will not	37	specific flavor of thread offered by this module also guarantees you that
38	switch between coroutines unless necessary, at easily-identified points	38	it will not switch between threads unless necessary, at easily-identified
39	in your program, so locking and parallel access are rarely an issue,	39	points in your program, so locking and parallel access are rarely an
40	making coroutine programming much safer and easier than using other thread	40	issue, making thread programming much safer and easier than using other
41	models.	41	thread models.
42		42
43	Unlike the so-called "Perl threads" (which are not actually real threads	43	Unlike the so-called "Perl threads" (which are not actually real threads
44	but only the windows process emulation ported to unix), Coro provides a	44	but only the windows process emulation (see section of same name for
		45	more details) ported to UNIX, and as such act as processes), Coro
45	full shared address space, which makes communication between coroutines	46	provides a full shared address space, which makes communication between
46	very easy. And coroutines are fast, too: disabling the Windows process	47	threads very easy. And coro threads are fast, too: disabling the Windows
47	emulation code in your perl and using Coro can easily result in a two to	48	process emulation code in your perl and using Coro can easily result in
48	four times speed increase for your programs.	49	a two to four times speed increase for your programs. A parallel matrix
		50	multiplication benchmark (very communication-intensive) runs over 300
		51	times faster on a single core than perls pseudo-threads on a quad core
		52	using all four cores.
49		53
50	Coro achieves that by supporting multiple running interpreters that share	54	Coro achieves that by supporting multiple running interpreters that share
51	data, which is especially useful to code pseudo-parallel processes and	55	data, which is especially useful to code pseudo-parallel processes and
52	for event-based programming, such as multiple HTTP-GET requests running	56	for event-based programming, such as multiple HTTP-GET requests running
53	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
54	into an event-based environment.	58	into an event-based environment.
55		59
56	In this module, a coroutines is defined as "callchain + lexical variables	60	In this module, a thread is defined as "callchain + lexical variables +
57	+ @_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own	61	some package variables + C stack), that is, a thread has its own callchain,
58	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
59	global variables (see L<Coro::State> for more configuration and background	63	variables (see L<Coro::State> for more configuration and background info).
60	info).
61		64
62	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
63	module family is quite large.	66	module family is quite large.
64		67
		68	=head1 CORO THREAD LIFE CYCLE
		69
		70	During the long and exciting (or not) life of a coro thread, it goes
		71	through a number of states:
		72
		73	=over 4
		74
		75	=item 1. Creation
		76
		77	The first thing in the life of a coro thread is it's creation -
		78	obviously. The typical way to create a thread is to call the C<async
		79	BLOCK> function:
		80
		81	async {
		82	# thread code goes here
		83	};
		84
		85	You can also pass arguments, which are put in C<@_>:
		86
		87	async {
		88	print $_[1]; # prints 2
		89	} 1, 2, 3;
		90
		91	This creates a new coro thread and puts it into the ready queue, meaning
		92	it will run as soon as the CPU is free for it.
		93
		94	C<async> will return a Coro object - you can store this for future
		95	reference or ignore it - a thread that is running, ready to run or waiting
		96	for some event is alive on it's own.
		97
		98	Another way to create a thread is to call the C<new> constructor with a
		99	code-reference:
		100
		101	new Coro sub {
		102	# thread code goes here
		103	}, @optional_arguments;
		104
		105	This is quite similar to calling C<async>, but the important difference is
		106	that the new thread is not put into the ready queue, so the thread will
		107	not run until somebody puts it there. C<async> is, therefore, identical to
		108	this sequence:
		109
		110	my $coro = new Coro sub {
		111	# thread code goes here
		112	};
		113	$coro->ready;
		114	return $coro;
		115
		116	=item 2. Startup
		117
		118	When a new coro thread is created, only a copy of the code reference
		119	and the arguments are stored, no extra memory for stacks and so on is
		120	allocated, keeping the coro thread in a low-memory state.
		121
		122	Only when it actually starts executing will all the resources be finally
		123	allocated.
		124
		125	The optional arguments specified at coro creation are available in C<@_>,
		126	similar to function calls.
		127
		128	=item 3. Running / Blocking
		129
		130	A lot can happen after the coro thread has started running. Quite usually,
		131	it will not run to the end in one go (because you could use a function
		132	instead), but it will give up the CPU regularly because it waits for
		133	external events.
		134
		135	As long as a coro thread runs, its Coro object is available in the global
		136	variable C<$Coro::current>.
		137
		138	The low-level way to give up the CPU is to call the scheduler, which
		139	selects a new coro thread to run:
		140
		141	Coro::schedule;
		142
		143	Since running threads are not in the ready queue, calling the scheduler
		144	without doing anything else will block the coro thread forever - you need
		145	to arrange either for the coro to put woken up (readied) by some other
		146	event or some other thread, or you can put it into the ready queue before
		147	scheduling:
		148
		149	# this is exactly what Coro::cede does
		150	$Coro::current->ready;
		151	Coro::schedule;
		152
		153	All the higher-level synchronisation methods (Coro::Semaphore,
		154	Coro::rouse_*...) are actually implemented via C<< ->ready >> and C<<
		155	Coro::schedule >>.
		156
		157	While the coro thread is running it also might get assigned a C-level
		158	thread, or the C-level thread might be unassigned from it, as the Coro
		159	runtime wishes. A C-level thread needs to be assigned when your perl
		160	thread calls into some C-level function and that function in turn calls
		161	perl and perl then wants to switch coroutines. This happens most often
		162	when you run an event loop and block in the callback, or when perl
		163	itself calls some function such as C<AUTOLOAD> or methods via the C<tie>
		164	mechanism.
		165
		166	=item 4. Termination
		167
		168	Many threads actually terminate after some time. There are a number of
		169	ways to terminate a coro thread, the simplest is returning from the
		170	top-level code reference:
		171
		172	async {
		173	# after returning from here, the coro thread is terminated
		174	};
		175
		176	async {
		177	return if 0.5 < rand; # terminate a little earlier, maybe
		178	print "got a chance to print this\n";
		179	# or here
		180	};
		181
		182	Any values returned from the coroutine can be recovered using C<< ->join
		183	>>:
		184
		185	my $coro = async {
		186	"hello, world\n" # return a string
		187	};
		188
		189	my $hello_world = $coro->join;
		190
		191	print $hello_world;
		192
		193	Another way to terminate is to call C<< Coro::terminate >>, which at any
		194	subroutine call nesting level:
		195
		196	async {
		197	Coro::terminate "return value 1", "return value 2";
		198	};
		199
		200	Yet another way is to C<< ->cancel >> (or C<< ->safe_cancel >>) the coro
		201	thread from another thread:
		202
		203	my $coro = async {
		204	exit 1;
		205	};
		206
		207	$coro->cancel; # also accepts values for ->join to retrieve
		208
		209	Cancellation I<can> be dangerous - it's a bit like calling C<exit> without
		210	actually exiting, and might leave C libraries and XS modules in a weird
		211	state. Unlike other thread implementations, however, Coro is exceptionally
		212	safe with regards to cancellation, as perl will always be in a consistent
		213	state, and for those cases where you want to do truly marvellous things
		214	with your coro while it is being cancelled - that is, make sure all
		215	cleanup code is executed from the thread being cancelled - there is even a
		216	C<< ->safe_cancel >> method.
		217
		218	So, cancelling a thread that runs in an XS event loop might not be the
		219	best idea, but any other combination that deals with perl only (cancelling
		220	when a thread is in a C<tie> method or an C<AUTOLOAD> for example) is
		221	safe.
		222
		223	Last not least, a coro thread object that isn't referenced is C<<
		224	->cancel >>'ed automatically - just like other objects in Perl. This
		225	is not such a common case, however - a running thread is referencedy by
		226	C<$Coro::current>, a thread ready to run is referenced by the ready queue,
		227	a thread waiting on a lock or semaphore is referenced by being in some
		228	wait list and so on. But a thread that isn't in any of those queues gets
		229	cancelled:
		230
		231	async {
		232	schedule; # cede to other coros, don't go into the ready queue
		233	};
		234
		235	cede;
		236	# now the async above is destroyed, as it is not referenced by anything.
		237
		238	A slightly embellished example might make it clearer:
		239
		240	async {
		241	my $guard = Guard::guard { print "destroyed\n" };
		242	schedule while 1;
		243	};
		244
		245	cede;
		246
		247	Superficially one might not expect any output - since the C<async>
		248	implements an endless loop, the C<$guard> will not be cleaned up. However,
		249	since the thread object returned by C<async> is not stored anywhere, the
		250	thread is initially referenced because it is in the ready queue, when it
		251	runs it is referenced by C<$Coro::current>, but when it calls C<schedule>,
		252	it gets C<cancel>ed causing the guard object to be destroyed (see the next
		253	section), and printing it's message.
		254
		255	If this seems a bit drastic, remember that this only happens when nothing
		256	references the thread anymore, which means there is no way to further
		257	execute it, ever. The only options at this point are leaking the thread,
		258	or cleaning it up, which brings us to...
		259
		260	=item 5. Cleanup
		261
		262	Threads will allocate various resources. Most but not all will be returned
		263	when a thread terminates, during clean-up.
		264
		265	Cleanup is quite similar to throwing an uncaught exception: perl will
		266	work it's way up through all subroutine calls and blocks. On it's way, it
		267	will release all C<my> variables, undo all C<local>'s and free any other
		268	resources truly local to the thread.
		269
		270	So, a common way to free resources is to keep them referenced only by my
		271	variables:
		272
		273	async {
		274	my $big_cache = new Cache ...;
		275	};
		276
		277	If there are no other references, then the C<$big_cache> object will be
		278	freed when the thread terminates, regardless of how it does so.
		279
		280	What it does C<NOT> do is unlock any Coro::Semaphores or similar
		281	resources, but that's where the C<guard> methods come in handy:
		282
		283	my $sem = new Coro::Semaphore;
		284
		285	async {
		286	my $lock_guard = $sem->guard;
		287	# if we return, or die or get cancelled, here,
		288	# then the semaphore will be "up"ed.
		289	};
		290
		291	The C<Guard::guard> function comes in handy for any custom cleanup you
		292	might want to do (but you cannot switch to other coroutines from those
		293	code blocks):
		294
		295	async {
		296	my $window = new Gtk2::Window "toplevel";
		297	# The window will not be cleaned up automatically, even when $window
		298	# gets freed, so use a guard to ensure it's destruction
		299	# in case of an error:
		300	my $window_guard = Guard::guard { $window->destroy };
		301
		302	# we are safe here
		303	};
		304
		305	Last not least, C<local> can often be handy, too, e.g. when temporarily
		306	replacing the coro thread description:
		307
		308	sub myfunction {
		309	local $Coro::current->{desc} = "inside myfunction(@_)";
		310
		311	# if we return or die here, the description will be restored
		312	}
		313
		314	=item 6. Viva La Zombie Muerte
		315
		316	Even after a thread has terminated and cleaned up its resources, the Coro
		317	object still is there and stores the return values of the thread.
		318
		319	When there are no other references, it will simply be cleaned up and
		320	freed.
		321
		322	If there areany references, the Coro object will stay around, and you
		323	can call C<< ->join >> as many times as you wish to retrieve the result
		324	values:
		325
		326	async {
		327	print "hi\n";
		328	1
		329	};
		330
		331	# run the async above, and free everything before returning
		332	# from Coro::cede:
		333	Coro::cede;
		334
		335	{
		336	my $coro = async {
		337	print "hi\n";
		338	1
		339	};
		340
		341	# run the async above, and clean up, but do not free the coro
		342	# object:
		343	Coro::cede;
		344
		345	# optionally retrieve the result values
		346	my @results = $coro->join;
		347
		348	# now $coro goes out of scope, and presumably gets freed
		349	};
		350
		351	=back
		352
65	=cut	353	=cut
66		354
67	package Coro;	355	package Coro;
68		356
69	use strict qw(vars subs);	357	use common::sense;
70	no warnings "uninitialized";	358
		359	use Carp ();
		360
		361	use Guard ();
71		362
72	use Coro::State;	363	use Coro::State;
73		364
74	use base qw(Coro::State Exporter);	365	use base qw(Coro::State Exporter);
75		366
76	our $idle; # idle handler	367	our $idle; # idle handler
77	our $main; # main coroutine	368	our $main; # main coro
78	our $current; # current coroutine	369	our $current; # current coro
79		370
80	our $VERSION = "5.0";	371	our $VERSION = 6.513;
81		372
82	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);	373	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait);
83	our %EXPORT_TAGS = (	374	our %EXPORT_TAGS = (
84	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],	375	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
85	);	376	);
86	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));	377	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));
87		378
…		…
89		380
90	=over 4	381	=over 4
91		382
92	=item $Coro::main	383	=item $Coro::main
93		384
94	This variable stores the coroutine object that represents the main	385	This variable stores the Coro object that represents the main
95	program. While you cna C<ready> it and do most other things you can do to	386	program. While you can C<ready> it and do most other things you can do to
96	coroutines, it is mainly useful to compare again C<$Coro::current>, to see	387	coro, it is mainly useful to compare again C<$Coro::current>, to see
97	whether you are running in the main program or not.	388	whether you are running in the main program or not.
98		389
99	=cut	390	=cut
100		391
101	# $main is now being initialised by Coro::State	392	# $main is now being initialised by Coro::State
102		393
103	=item $Coro::current	394	=item $Coro::current
104		395
105	The coroutine object representing the current coroutine (the last	396	The Coro object representing the current coro (the last
106	coroutine that the Coro scheduler switched to). The initial value is	397	coro that the Coro scheduler switched to). The initial value is
107	C<$Coro::main> (of course).	398	C<$Coro::main> (of course).
108		399
109	This variable is B<strictly> I<read-only>. You can take copies of the	400	This variable is B<strictly> I<read-only>. You can take copies of the
110	value stored in it and use it as any other coroutine object, but you must	401	value stored in it and use it as any other Coro object, but you must
111	not otherwise modify the variable itself.	402	not otherwise modify the variable itself.
112		403
113	=cut	404	=cut
114		405
115	sub current() { $current } # [DEPRECATED]	406	sub current() { $current } # [DEPRECATED]
116		407
117	=item $Coro::idle	408	=item $Coro::idle
118		409
119	This variable is mainly useful to integrate Coro into event loops. It is	410	This variable is mainly useful to integrate Coro into event loops. It is
120	usually better to rely on L<Coro::AnyEvent> or LC<Coro::EV>, as this is	411	usually better to rely on L<Coro::AnyEvent> or L<Coro::EV>, as this is
121	pretty low-level functionality.	412	pretty low-level functionality.
122		413
123	This variable stores a callback that is called whenever the scheduler	414	This variable stores a Coro object that is put into the ready queue when
124	finds no ready coroutines to run. The default implementation prints	415	there are no other ready threads (without invoking any ready hooks).
125	"FATAL: deadlock detected" and exits, because the program has no other way
126	to continue.
127		416
		417	The default implementation dies with "FATAL: deadlock detected.", followed
		418	by a thread listing, because the program has no other way to continue.
		419
128	This hook is overwritten by modules such as C<Coro::Timer> and	420	This hook is overwritten by modules such as C<Coro::EV> and
129	C<Coro::AnyEvent> to wait on an external event that hopefully wake up a	421	C<Coro::AnyEvent> to wait on an external event that hopefully wakes up a
130	coroutine so the scheduler can run it.	422	coro so the scheduler can run it.
131		423
132	Note that the callback I<must not>, under any circumstances, block
133	the current coroutine. Normally, this is achieved by having an "idle
134	coroutine" that calls the event loop and then blocks again, and then
135	readying that coroutine in the idle handler.
136
137	See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this	424	See L<Coro::EV> or L<Coro::AnyEvent> for examples of using this technique.
138	technique.
139
140	Please note that if your callback recursively invokes perl (e.g. for event
141	handlers), then it must be prepared to be called recursively itself.
142		425
143	=cut	426	=cut
144		427
145	$idle = sub {	428	# \|\|= because other modules could have provided their own by now
146	require Carp;	429	$idle \|\|= new Coro sub {
147	Carp::croak ("FATAL: deadlock detected");	430	require Coro::Debug;
		431	die "FATAL: deadlock detected.\n"
		432	. Coro::Debug::ps_listing ();
148	};	433	};
149		434
150	# this coroutine is necessary because a coroutine	435	# this coro is necessary because a coro
151	# cannot destroy itself.	436	# cannot destroy itself.
152	our @destroy;	437	our @destroy;
153	our $manager;	438	our $manager;
154		439
155	$manager = new Coro sub {	440	$manager = new Coro sub {
156	while () {	441	while () {
157	Coro::_cancel shift @destroy	442	_destroy shift @destroy
158	while @destroy;	443	while @destroy;
159		444
160	&schedule;	445	&schedule;
161	}	446	}
162	};	447	};
163	$manager->{desc} = "[coro manager]";	448	$manager->{desc} = "[coro manager]";
164	$manager->prio (PRIO_MAX);	449	$manager->prio (PRIO_MAX);
165		450
166	=back	451	=back
167		452
168	=head1 SIMPLE COROUTINE CREATION	453	=head1 SIMPLE CORO CREATION
169		454
170	=over 4	455	=over 4
171		456
172	=item async { ... } [@args...]	457	=item async { ... } [@args...]
173		458
174	Create a new coroutine and return it's coroutine object (usually	459	Create a new coro and return its Coro object (usually
175	unused). The coroutine will be put into the ready queue, so	460	unused). The coro will be put into the ready queue, so
176	it will start running automatically on the next scheduler run.	461	it will start running automatically on the next scheduler run.
177		462
178	The first argument is a codeblock/closure that should be executed in the	463	The first argument is a codeblock/closure that should be executed in the
179	coroutine. When it returns argument returns the coroutine is automatically	464	coro. When it returns argument returns the coro is automatically
180	terminated.	465	terminated.
181		466
182	The remaining arguments are passed as arguments to the closure.	467	The remaining arguments are passed as arguments to the closure.
183		468
184	See the C<Coro::State::new> constructor for info about the coroutine	469	See the C<Coro::State::new> constructor for info about the coro
185	environment in which coroutines are executed.	470	environment in which coro are executed.
186		471
187	Calling C<exit> in a coroutine will do the same as calling exit outside	472	Calling C<exit> in a coro will do the same as calling exit outside
188	the coroutine. Likewise, when the coroutine dies, the program will exit,	473	the coro. Likewise, when the coro dies, the program will exit,
189	just as it would in the main program.	474	just as it would in the main program.
190		475
191	If you do not want that, you can provide a default C<die> handler, or	476	If you do not want that, you can provide a default C<die> handler, or
192	simply avoid dieing (by use of C<eval>).	477	simply avoid dieing (by use of C<eval>).
193		478
194	Example: Create a new coroutine that just prints its arguments.	479	Example: Create a new coro that just prints its arguments.
195		480
196	async {	481	async {
197	print "@_\n";	482	print "@_\n";
198	} 1,2,3,4;	483	} 1,2,3,4;
199		484
200	=cut
201
202	sub async(&@) {
203	my $coro = new Coro @_;
204	$coro->ready;
205	$coro
206	}
207
208	=item async_pool { ... } [@args...]	485	=item async_pool { ... } [@args...]
209		486
210	Similar to C<async>, but uses a coroutine pool, so you should not call	487	Similar to C<async>, but uses a coro pool, so you should not call
211	terminate or join on it (although you are allowed to), and you get a	488	terminate or join on it (although you are allowed to), and you get a
212	coroutine that might have executed other code already (which can be good	489	coro that might have executed other code already (which can be good
213	or bad :).	490	or bad :).
214		491
215	On the plus side, this function is about twice as fast as creating (and	492	On the plus side, this function is about twice as fast as creating (and
216	destroying) a completely new coroutine, so if you need a lot of generic	493	destroying) a completely new coro, so if you need a lot of generic
217	coroutines in quick successsion, use C<async_pool>, not C<async>.	494	coros in quick successsion, use C<async_pool>, not C<async>.
218		495
219	The code block is executed in an C<eval> context and a warning will be	496	The code block is executed in an C<eval> context and a warning will be
220	issued in case of an exception instead of terminating the program, as	497	issued in case of an exception instead of terminating the program, as
221	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>	498	C<async> does. As the coro is being reused, stuff like C<on_destroy>
222	will not work in the expected way, unless you call terminate or cancel,	499	will not work in the expected way, unless you call terminate or cancel,
223	which somehow defeats the purpose of pooling (but is fine in the	500	which somehow defeats the purpose of pooling (but is fine in the
224	exceptional case).	501	exceptional case).
225		502
226	The priority will be reset to C<0> after each run, tracing will be	503	The priority will be reset to C<0> after each run, all C<swap_sv> calls
227	disabled, the description will be reset and the default output filehandle	504	will be undone, tracing will be disabled, the description will be reset
228	gets restored, so you can change all these. Otherwise the coroutine will	505	and the default output filehandle gets restored, so you can change all
229	be re-used "as-is": most notably if you change other per-coroutine global	506	these. Otherwise the coro will be re-used "as-is": most notably if you
230	stuff such as C<$/> you I<must needs> revert that change, which is most	507	change other per-coro global stuff such as C<$/> you I<must needs> revert
231	simply done by using local as in: C<< local $/ >>.	508	that change, which is most simply done by using local as in: C<< local $/
		509	>>.
232		510
233	The idle pool size is limited to C<8> idle coroutines (this can be	511	The idle pool size is limited to C<8> idle coros (this can be
234	adjusted by changing $Coro::POOL_SIZE), but there can be as many non-idle	512	adjusted by changing $Coro::POOL_SIZE), but there can be as many non-idle
235	coros as required.	513	coros as required.
236		514
237	If you are concerned about pooled coroutines growing a lot because a	515	If you are concerned about pooled coros growing a lot because a
238	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool	516	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
239	{ terminate }> once per second or so to slowly replenish the pool. In	517	{ terminate }> once per second or so to slowly replenish the pool. In
240	addition to that, when the stacks used by a handler grows larger than 32kb	518	addition to that, when the stacks used by a handler grows larger than 32kb
241	(adjustable via $Coro::POOL_RSS) it will also be destroyed.	519	(adjustable via $Coro::POOL_RSS) it will also be destroyed.
242		520
…		…
259	=back	537	=back
260		538
261	=head1 STATIC METHODS	539	=head1 STATIC METHODS
262		540
263	Static methods are actually functions that implicitly operate on the	541	Static methods are actually functions that implicitly operate on the
264	current coroutine.	542	current coro.
265		543
266	=over 4	544	=over 4
267		545
268	=item schedule	546	=item schedule
269		547
270	Calls the scheduler. The scheduler will find the next coroutine that is	548	Calls the scheduler. The scheduler will find the next coro that is
271	to be run from the ready queue and switches to it. The next coroutine	549	to be run from the ready queue and switches to it. The next coro
272	to be run is simply the one with the highest priority that is longest	550	to be run is simply the one with the highest priority that is longest
273	in its ready queue. If there is no coroutine ready, it will clal the	551	in its ready queue. If there is no coro ready, it will call the
274	C<$Coro::idle> hook.	552	C<$Coro::idle> hook.
275		553
276	Please note that the current coroutine will I<not> be put into the ready	554	Please note that the current coro will I<not> be put into the ready
277	queue, so calling this function usually means you will never be called	555	queue, so calling this function usually means you will never be called
278	again unless something else (e.g. an event handler) calls C<< ->ready >>,	556	again unless something else (e.g. an event handler) calls C<< ->ready >>,
279	thus waking you up.	557	thus waking you up.
280		558
281	This makes C<schedule> I<the> generic method to use to block the current	559	This makes C<schedule> I<the> generic method to use to block the current
282	coroutine and wait for events: first you remember the current coroutine in	560	coro and wait for events: first you remember the current coro in
283	a variable, then arrange for some callback of yours to call C<< ->ready	561	a variable, then arrange for some callback of yours to call C<< ->ready
284	>> on that once some event happens, and last you call C<schedule> to put	562	>> on that once some event happens, and last you call C<schedule> to put
285	yourself to sleep. Note that a lot of things can wake your coroutine up,	563	yourself to sleep. Note that a lot of things can wake your coro up,
286	so you need to check whether the event indeed happened, e.g. by storing the	564	so you need to check whether the event indeed happened, e.g. by storing the
287	status in a variable.	565	status in a variable.
288		566
289	See B<HOW TO WAIT FOR A CALLBACK>, below, for some ways to wait for callbacks.	567	See B<HOW TO WAIT FOR A CALLBACK>, below, for some ways to wait for callbacks.
290		568
291	=item cede	569	=item cede
292		570
293	"Cede" to other coroutines. This function puts the current coroutine into	571	"Cede" to other coros. This function puts the current coro into
294	the ready queue and calls C<schedule>, which has the effect of giving	572	the ready queue and calls C<schedule>, which has the effect of giving
295	up the current "timeslice" to other coroutines of the same or higher	573	up the current "timeslice" to other coros of the same or higher
296	priority. Once your coroutine gets its turn again it will automatically be	574	priority. Once your coro gets its turn again it will automatically be
297	resumed.	575	resumed.
298		576
299	This function is often called C<yield> in other languages.	577	This function is often called C<yield> in other languages.
300		578
301	=item Coro::cede_notself	579	=item Coro::cede_notself
302		580
303	Works like cede, but is not exported by default and will cede to I<any>	581	Works like cede, but is not exported by default and will cede to I<any>
304	coroutine, regardless of priority. This is useful sometimes to ensure	582	coro, regardless of priority. This is useful sometimes to ensure
305	progress is made.	583	progress is made.
306		584
307	=item terminate [arg...]	585	=item terminate [arg...]
308		586
309	Terminates the current coroutine with the given status values (see L<cancel>).	587	Terminates the current coro with the given status values (see
		588	L<cancel>). The values will not be copied, but referenced directly.
		589
		590	=item Coro::on_enter BLOCK, Coro::on_leave BLOCK
		591
		592	These function install enter and leave winders in the current scope. The
		593	enter block will be executed when on_enter is called and whenever the
		594	current coro is re-entered by the scheduler, while the leave block is
		595	executed whenever the current coro is blocked by the scheduler, and
		596	also when the containing scope is exited (by whatever means, be it exit,
		597	die, last etc.).
		598
		599	I<Neither invoking the scheduler, nor exceptions, are allowed within those
		600	BLOCKs>. That means: do not even think about calling C<die> without an
		601	eval, and do not even think of entering the scheduler in any way.
		602
		603	Since both BLOCKs are tied to the current scope, they will automatically
		604	be removed when the current scope exits.
		605
		606	These functions implement the same concept as C<dynamic-wind> in scheme
		607	does, and are useful when you want to localise some resource to a specific
		608	coro.
		609
		610	They slow down thread switching considerably for coros that use them
		611	(about 40% for a BLOCK with a single assignment, so thread switching is
		612	still reasonably fast if the handlers are fast).
		613
		614	These functions are best understood by an example: The following function
		615	will change the current timezone to "Antarctica/South_Pole", which
		616	requires a call to C<tzset>, but by using C<on_enter> and C<on_leave>,
		617	which remember/change the current timezone and restore the previous
		618	value, respectively, the timezone is only changed for the coro that
		619	installed those handlers.
		620
		621	use POSIX qw(tzset);
		622
		623	async {
		624	my $old_tz; # store outside TZ value here
		625
		626	Coro::on_enter {
		627	$old_tz = $ENV{TZ}; # remember the old value
		628
		629	$ENV{TZ} = "Antarctica/South_Pole";
		630	tzset; # enable new value
		631	};
		632
		633	Coro::on_leave {
		634	$ENV{TZ} = $old_tz;
		635	tzset; # restore old value
		636	};
		637
		638	# at this place, the timezone is Antarctica/South_Pole,
		639	# without disturbing the TZ of any other coro.
		640	};
		641
		642	This can be used to localise about any resource (locale, uid, current
		643	working directory etc.) to a block, despite the existence of other
		644	coros.
		645
		646	Another interesting example implements time-sliced multitasking using
		647	interval timers (this could obviously be optimised, but does the job):
		648
		649	# "timeslice" the given block
		650	sub timeslice(&) {
		651	use Time::HiRes ();
		652
		653	Coro::on_enter {
		654	# on entering the thread, we set an VTALRM handler to cede
		655	$SIG{VTALRM} = sub { cede };
		656	# and then start the interval timer
		657	Time::HiRes::setitimer &Time::HiRes::ITIMER_VIRTUAL, 0.01, 0.01;
		658	};
		659	Coro::on_leave {
		660	# on leaving the thread, we stop the interval timer again
		661	Time::HiRes::setitimer &Time::HiRes::ITIMER_VIRTUAL, 0, 0;
		662	};
		663
		664	&{+shift};
		665	}
		666
		667	# use like this:
		668	timeslice {
		669	# The following is an endless loop that would normally
		670	# monopolise the process. Since it runs in a timesliced
		671	# environment, it will regularly cede to other threads.
		672	while () { }
		673	};
		674
310		675
311	=item killall	676	=item killall
312		677
313	Kills/terminates/cancels all coroutines except the currently running	678	Kills/terminates/cancels all coros except the currently running one.
314	one. This is useful after a fork, either in the child or the parent, as
315	usually only one of them should inherit the running coroutines.
316		679
317	Note that while this will try to free some of the main programs resources,	680	Note that while this will try to free some of the main interpreter
		681	resources if the calling coro isn't the main coro, but one
318	you cannot free all of them, so if a coroutine that is not the main	682	cannot free all of them, so if a coro that is not the main coro
319	program calls this function, there will be some one-time resource leak.	683	calls this function, there will be some one-time resource leak.
320		684
321	=cut	685	=cut
322		686
323	sub killall {	687	sub killall {
324	for (Coro::State::list) {	688	for (Coro::State::list) {
…		…
327	}	691	}
328	}	692	}
329		693
330	=back	694	=back
331		695
332	=head1 COROUTINE OBJECT METHODS	696	=head1 CORO OBJECT METHODS
333		697
334	These are the methods you can call on coroutine objects (or to create	698	These are the methods you can call on coro objects (or to create
335	them).	699	them).
336		700
337	=over 4	701	=over 4
338		702
339	=item new Coro \&sub [, @args...]	703	=item new Coro \&sub [, @args...]
340		704
341	Create a new coroutine and return it. When the sub returns, the coroutine	705	Create a new coro and return it. When the sub returns, the coro
342	automatically terminates as if C<terminate> with the returned values were	706	automatically terminates as if C<terminate> with the returned values were
343	called. To make the coroutine run you must first put it into the ready	707	called. To make the coro run you must first put it into the ready
344	queue by calling the ready method.	708	queue by calling the ready method.
345		709
346	See C<async> and C<Coro::State::new> for additional info about the	710	See C<async> and C<Coro::State::new> for additional info about the
347	coroutine environment.	711	coro environment.
348		712
349	=cut	713	=cut
350		714
351	sub _terminate {	715	sub _coro_run {
352	terminate &{+shift};	716	terminate &{+shift};
353	}	717	}
354		718
355	=item $success = $coroutine->ready	719	=item $success = $coro->ready
356		720
357	Put the given coroutine into the end of its ready queue (there is one	721	Put the given coro into the end of its ready queue (there is one
358	queue for each priority) and return true. If the coroutine is already in	722	queue for each priority) and return true. If the coro is already in
359	the ready queue, do nothing and return false.	723	the ready queue, do nothing and return false.
360		724
361	This ensures that the scheduler will resume this coroutine automatically	725	This ensures that the scheduler will resume this coro automatically
362	once all the coroutines of higher priority and all coroutines of the same	726	once all the coro of higher priority and all coro of the same
363	priority that were put into the ready queue earlier have been resumed.	727	priority that were put into the ready queue earlier have been resumed.
364		728
		729	=item $coro->suspend
		730
		731	Suspends the specified coro. A suspended coro works just like any other
		732	coro, except that the scheduler will not select a suspended coro for
		733	execution.
		734
		735	Suspending a coro can be useful when you want to keep the coro from
		736	running, but you don't want to destroy it, or when you want to temporarily
		737	freeze a coro (e.g. for debugging) to resume it later.
		738
		739	A scenario for the former would be to suspend all (other) coros after a
		740	fork and keep them alive, so their destructors aren't called, but new
		741	coros can be created.
		742
		743	=item $coro->resume
		744
		745	If the specified coro was suspended, it will be resumed. Note that when
		746	the coro was in the ready queue when it was suspended, it might have been
		747	unreadied by the scheduler, so an activation might have been lost.
		748
		749	To avoid this, it is best to put a suspended coro into the ready queue
		750	unconditionally, as every synchronisation mechanism must protect itself
		751	against spurious wakeups, and the one in the Coro family certainly do
		752	that.
		753
		754	=item $state->is_new
		755
		756	Returns true iff this Coro object is "new", i.e. has never been run
		757	yet. Those states basically consist of only the code reference to call and
		758	the arguments, but consumes very little other resources. New states will
		759	automatically get assigned a perl interpreter when they are transferred to.
		760
		761	=item $state->is_zombie
		762
		763	Returns true iff the Coro object has been cancelled, i.e.
		764	it's resources freed because they were C<cancel>'ed, C<terminate>'d,
		765	C<safe_cancel>'ed or simply went out of scope.
		766
		767	The name "zombie" stems from UNIX culture, where a process that has
		768	exited and only stores and exit status and no other resources is called a
		769	"zombie".
		770
365	=item $is_ready = $coroutine->is_ready	771	=item $is_ready = $coro->is_ready
366		772
367	Return whether the coroutine is currently the ready queue or not,	773	Returns true iff the Coro object is in the ready queue. Unless the Coro
		774	object gets destroyed, it will eventually be scheduled by the scheduler.
368		775
		776	=item $is_running = $coro->is_running
		777
		778	Returns true iff the Coro object is currently running. Only one Coro object
		779	can ever be in the running state (but it currently is possible to have
		780	multiple running Coro::States).
		781
		782	=item $is_suspended = $coro->is_suspended
		783
		784	Returns true iff this Coro object has been suspended. Suspended Coros will
		785	not ever be scheduled.
		786
369	=item $coroutine->cancel (arg...)	787	=item $coro->cancel (arg...)
370		788
371	Terminates the given coroutine and makes it return the given arguments as	789	Terminates the given Coro thread and makes it return the given arguments as
372	status (default: the empty list). Never returns if the coroutine is the	790	status (default: an empty list). Never returns if the Coro is the
373	current coroutine.	791	current Coro.
374		792
375	=cut	793	This is a rather brutal way to free a coro, with some limitations - if
		794	the thread is inside a C callback that doesn't expect to be canceled,
		795	bad things can happen, or if the cancelled thread insists on running
		796	complicated cleanup handlers that rely on its thread context, things will
		797	not work.
376		798
377	sub cancel {	799	Any cleanup code being run (e.g. from C<guard> blocks, destructors and so
378	my $self = shift;	800	on) will be run without a thread context, and is not allowed to switch
		801	to other threads. A common mistake is to call C<< ->cancel >> from a
		802	destructor called by die'ing inside the thread to be cancelled for
		803	example.
379		804
380	if ($current == $self) {	805	On the plus side, C<< ->cancel >> will always clean up the thread, no
381	terminate @_;	806	matter what. If your cleanup code is complex or you want to avoid
382	} else {	807	cancelling a C-thread that doesn't know how to clean up itself, it can be
383	$self->{_status} = [@_];	808	better to C<< ->throw >> an exception, or use C<< ->safe_cancel >>.
384	$self->_cancel;	809
		810	The arguments to C<< ->cancel >> are not copied, but instead will
		811	be referenced directly (e.g. if you pass C<$var> and after the call
		812	change that variable, then you might change the return values passed to
		813	e.g. C<join>, so don't do that).
		814
		815	The resources of the Coro are usually freed (or destructed) before this
		816	call returns, but this can be delayed for an indefinite amount of time, as
		817	in some cases the manager thread has to run first to actually destruct the
		818	Coro object.
		819
		820	=item $coro->safe_cancel ($arg...)
		821
		822	Works mostly like C<< ->cancel >>, but is inherently "safer", and
		823	consequently, can fail with an exception in cases the thread is not in a
		824	cancellable state. Essentially, C<< ->safe_cancel >> is a C<< ->cancel >>
		825	with extra checks before canceling.
		826
		827	It works a bit like throwing an exception that cannot be caught -
		828	specifically, it will clean up the thread from within itself, so all
		829	cleanup handlers (e.g. C<guard> blocks) are run with full thread
		830	context and can block if they wish. The downside is that there is no
		831	guarantee that the thread can be cancelled when you call this method, and
		832	therefore, it might fail. It is also considerably slower than C<cancel> or
		833	C<terminate>.
		834
		835	A thread is in a safe-cancellable state if it either hasn't been run yet,
		836	or it has no C context attached and is inside an SLF function.
		837
		838	The latter two basically mean that the thread isn't currently inside a
		839	perl callback called from some C function (usually via some XS modules)
		840	and isn't currently executing inside some C function itself (via Coro's XS
		841	API).
		842
		843	This call returns true when it could cancel the thread, or croaks with an
		844	error otherwise (i.e. it either returns true or doesn't return at all).
		845
		846	Why the weird interface? Well, there are two common models on how and
		847	when to cancel things. In the first, you have the expectation that your
		848	coro thread can be cancelled when you want to cancel it - if the thread
		849	isn't cancellable, this would be a bug somewhere, so C<< ->safe_cancel >>
		850	croaks to notify of the bug.
		851
		852	In the second model you sometimes want to ask nicely to cancel a thread,
		853	but if it's not a good time, well, then don't cancel. This can be done
		854	relatively easy like this:
		855
		856	if (! eval { $coro->safe_cancel }) {
		857	warn "unable to cancel thread: $@";
385	}	858	}
386	}
387		859
		860	However, what you never should do is first try to cancel "safely" and
		861	if that fails, cancel the "hard" way with C<< ->cancel >>. That makes
		862	no sense: either you rely on being able to execute cleanup code in your
		863	thread context, or you don't. If you do, then C<< ->safe_cancel >> is the
		864	only way, and if you don't, then C<< ->cancel >> is always faster and more
		865	direct.
		866
388	=item $coroutine->schedule_to	867	=item $coro->schedule_to
389		868
390	Puts the current coroutine to sleep (like C<Coro::schedule>), but instead	869	Puts the current coro to sleep (like C<Coro::schedule>), but instead
391	of continuing with the next coro from the ready queue, always switch to	870	of continuing with the next coro from the ready queue, always switch to
392	the given coroutine object (regardless of priority etc.). The readyness	871	the given coro object (regardless of priority etc.). The readyness
393	state of that coroutine isn't changed.	872	state of that coro isn't changed.
394		873
395	This is an advanced method for special cases - I'd love to hear about any	874	This is an advanced method for special cases - I'd love to hear about any
396	uses for this one.	875	uses for this one.
397		876
398	=item $coroutine->cede_to	877	=item $coro->cede_to
399		878
400	Like C<schedule_to>, but puts the current coroutine into the ready	879	Like C<schedule_to>, but puts the current coro into the ready
401	queue. This has the effect of temporarily switching to the given	880	queue. This has the effect of temporarily switching to the given
402	coroutine, and continuing some time later.	881	coro, and continuing some time later.
403		882
404	This is an advanced method for special cases - I'd love to hear about any	883	This is an advanced method for special cases - I'd love to hear about any
405	uses for this one.	884	uses for this one.
406		885
407	=item $coroutine->throw ([$scalar])	886	=item $coro->throw ([$scalar])
408		887
409	If C<$throw> is specified and defined, it will be thrown as an exception	888	If C<$throw> is specified and defined, it will be thrown as an exception
410	inside the coroutine at the next convenient point in time. Otherwise	889	inside the coro at the next convenient point in time. Otherwise
411	clears the exception object.	890	clears the exception object.
412		891
413	Coro will check for the exception each time a schedule-like-function	892	Coro will check for the exception each time a schedule-like-function
414	returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down	893	returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down
415	>>, C<< Coro::Handle->readable >> and so on. Most of these functions	894	>>, C<< Coro::Handle->readable >> and so on. Most of those functions (all
416	detect this case and return early in case an exception is pending.	895	that are part of Coro itself) detect this case and return early in case an
		896	exception is pending.
417		897
418	The exception object will be thrown "as is" with the specified scalar in	898	The exception object will be thrown "as is" with the specified scalar in
419	C<$@>, i.e. if it is a string, no line number or newline will be appended	899	C<$@>, i.e. if it is a string, no line number or newline will be appended
420	(unlike with C<die>).	900	(unlike with C<die>).
421		901
422	This can be used as a softer means than C<cancel> to ask a coroutine to	902	This can be used as a softer means than either C<cancel> or C<safe_cancel
423	end itself, although there is no guarantee that the exception will lead to	903	>to ask a coro to end itself, although there is no guarantee that the
424	termination, and if the exception isn't caught it might well end the whole	904	exception will lead to termination, and if the exception isn't caught it
425	program.	905	might well end the whole program.
426		906
427	You might also think of C<throw> as being the moral equivalent of	907	You might also think of C<throw> as being the moral equivalent of
428	C<kill>ing a coroutine with a signal (in this case, a scalar).	908	C<kill>ing a coro with a signal (in this case, a scalar).
429		909
430	=item $coroutine->join	910	=item $coro->join
431		911
432	Wait until the coroutine terminates and return any values given to the	912	Wait until the coro terminates and return any values given to the
433	C<terminate> or C<cancel> functions. C<join> can be called concurrently	913	C<terminate> or C<cancel> functions. C<join> can be called concurrently
434	from multiple coroutines, and all will be resumed and given the status	914	from multiple threads, and all will be resumed and given the status
435	return once the C<$coroutine> terminates.	915	return once the C<$coro> terminates.
436		916
437	=cut
438
439	sub join {
440	my $self = shift;
441
442	unless ($self->{_status}) {
443	my $current = $current;
444
445	push @{$self->{_on_destroy}}, sub {
446	$current->ready;
447	undef $current;
448	};
449
450	&schedule while $current;
451	}
452
453	wantarray ? @{$self->{_status}} : $self->{_status}[0];
454	}
455
456	=item $coroutine->on_destroy (\&cb)	917	=item $coro->on_destroy (\&cb)
457		918
458	Registers a callback that is called when this coroutine gets destroyed,	919	Registers a callback that is called when this coro thread gets destroyed,
459	but before it is joined. The callback gets passed the terminate arguments,	920	that is, after it's resources have been freed but before it is joined. The
		921	callback gets passed the terminate/cancel arguments, if any, and I<must
460	if any, and I<must not> die, under any circumstances.	922	not> die, under any circumstances.
461		923
462	=cut	924	There can be any number of C<on_destroy> callbacks per coro, and there is
		925	currently no way to remove a callback once added.
463		926
464	sub on_destroy {
465	my ($self, $cb) = @_;
466
467	push @{ $self->{_on_destroy} }, $cb;
468	}
469
470	=item $oldprio = $coroutine->prio ($newprio)	927	=item $oldprio = $coro->prio ($newprio)
471		928
472	Sets (or gets, if the argument is missing) the priority of the	929	Sets (or gets, if the argument is missing) the priority of the
473	coroutine. Higher priority coroutines get run before lower priority	930	coro thread. Higher priority coro get run before lower priority
474	coroutines. Priorities are small signed integers (currently -4 .. +3),	931	coros. Priorities are small signed integers (currently -4 .. +3),
475	that you can refer to using PRIO_xxx constants (use the import tag :prio	932	that you can refer to using PRIO_xxx constants (use the import tag :prio
476	to get then):	933	to get then):
477		934
478	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN	935	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
479	3 > 1 > 0 > -1 > -3 > -4	936	3 > 1 > 0 > -1 > -3 > -4
480		937
481	# set priority to HIGH	938	# set priority to HIGH
482	current->prio(PRIO_HIGH);	939	current->prio (PRIO_HIGH);
483		940
484	The idle coroutine ($Coro::idle) always has a lower priority than any	941	The idle coro thread ($Coro::idle) always has a lower priority than any
485	existing coroutine.	942	existing coro.
486		943
487	Changing the priority of the current coroutine will take effect immediately,	944	Changing the priority of the current coro will take effect immediately,
488	but changing the priority of coroutines in the ready queue (but not	945	but changing the priority of a coro in the ready queue (but not running)
489	running) will only take effect after the next schedule (of that	946	will only take effect after the next schedule (of that coro). This is a
490	coroutine). This is a bug that will be fixed in some future version.	947	bug that will be fixed in some future version.
491		948
492	=item $newprio = $coroutine->nice ($change)	949	=item $newprio = $coro->nice ($change)
493		950
494	Similar to C<prio>, but subtract the given value from the priority (i.e.	951	Similar to C<prio>, but subtract the given value from the priority (i.e.
495	higher values mean lower priority, just as in unix).	952	higher values mean lower priority, just as in UNIX's nice command).
496		953
497	=item $olddesc = $coroutine->desc ($newdesc)	954	=item $olddesc = $coro->desc ($newdesc)
498		955
499	Sets (or gets in case the argument is missing) the description for this	956	Sets (or gets in case the argument is missing) the description for this
500	coroutine. This is just a free-form string you can associate with a	957	coro thread. This is just a free-form string you can associate with a
501	coroutine.	958	coro.
502		959
503	This method simply sets the C<< $coroutine->{desc} >> member to the given	960	This method simply sets the C<< $coro->{desc} >> member to the given
504	string. You can modify this member directly if you wish.	961	string. You can modify this member directly if you wish, and in fact, this
		962	is often preferred to indicate major processing states that can then be
		963	seen for example in a L<Coro::Debug> session:
		964
		965	sub my_long_function {
		966	local $Coro::current->{desc} = "now in my_long_function";
		967	...
		968	$Coro::current->{desc} = "my_long_function: phase 1";
		969	...
		970	$Coro::current->{desc} = "my_long_function: phase 2";
		971	...
		972	}
505		973
506	=cut	974	=cut
507		975
508	sub desc {	976	sub desc {
509	my $old = $_[0]{desc};	977	my $old = $_[0]{desc};
…		…
522		990
523	=over 4	991	=over 4
524		992
525	=item Coro::nready	993	=item Coro::nready
526		994
527	Returns the number of coroutines that are currently in the ready state,	995	Returns the number of coro that are currently in the ready state,
528	i.e. that can be switched to by calling C<schedule> directory or	996	i.e. that can be switched to by calling C<schedule> directory or
529	indirectly. The value C<0> means that the only runnable coroutine is the	997	indirectly. The value C<0> means that the only runnable coro is the
530	currently running one, so C<cede> would have no effect, and C<schedule>	998	currently running one, so C<cede> would have no effect, and C<schedule>
531	would cause a deadlock unless there is an idle handler that wakes up some	999	would cause a deadlock unless there is an idle handler that wakes up some
532	coroutines.	1000	coro.
533		1001
534	=item my $guard = Coro::guard { ... }	1002	=item my $guard = Coro::guard { ... }
535		1003
536	This creates and returns a guard object. Nothing happens until the object	1004	This function still exists, but is deprecated. Please use the
537	gets destroyed, in which case the codeblock given as argument will be	1005	C<Guard::guard> function instead.
538	executed. This is useful to free locks or other resources in case of a
539	runtime error or when the coroutine gets canceled, as in both cases the
540	guard block will be executed. The guard object supports only one method,
541	C<< ->cancel >>, which will keep the codeblock from being executed.
542
543	Example: set some flag and clear it again when the coroutine gets canceled
544	or the function returns:
545
546	sub do_something {
547	my $guard = Coro::guard { $busy = 0 };
548	$busy = 1;
549
550	# do something that requires $busy to be true
551	}
552		1006
553	=cut	1007	=cut
554		1008
555	sub guard(&) {	1009	BEGIN { *guard = \&Guard::guard }
556	bless \(my $cb = $_[0]), "Coro::guard"
557	}
558
559	sub Coro::guard::cancel {
560	${$_[0]} = sub { };
561	}
562
563	sub Coro::guard::DESTROY {
564	${$_[0]}->();
565	}
566
567		1010
568	=item unblock_sub { ... }	1011	=item unblock_sub { ... }
569		1012
570	This utility function takes a BLOCK or code reference and "unblocks" it,	1013	This utility function takes a BLOCK or code reference and "unblocks" it,
571	returning a new coderef. Unblocking means that calling the new coderef	1014	returning a new coderef. Unblocking means that calling the new coderef
572	will return immediately without blocking, returning nothing, while the	1015	will return immediately without blocking, returning nothing, while the
573	original code ref will be called (with parameters) from within another	1016	original code ref will be called (with parameters) from within another
574	coroutine.	1017	coro.
575		1018
576	The reason this function exists is that many event libraries (such as the	1019	The reason this function exists is that many event libraries (such as
577	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form	1020	the venerable L<Event\|Event> module) are not thread-safe (a weaker form
578	of thread-safety). This means you must not block within event callbacks,	1021	of reentrancy). This means you must not block within event callbacks,
579	otherwise you might suffer from crashes or worse. The only event library	1022	otherwise you might suffer from crashes or worse. The only event library
580	currently known that is safe to use without C<unblock_sub> is L<EV>.	1023	currently known that is safe to use without C<unblock_sub> is L<EV> (but
		1024	you might still run into deadlocks if all event loops are blocked).
		1025
		1026	Coro will try to catch you when you block in the event loop
		1027	("FATAL: $Coro::idle blocked itself"), but this is just best effort and
		1028	only works when you do not run your own event loop.
581		1029
582	This function allows your callbacks to block by executing them in another	1030	This function allows your callbacks to block by executing them in another
583	coroutine where it is safe to block. One example where blocking is handy	1031	coro where it is safe to block. One example where blocking is handy
584	is when you use the L<Coro::AIO\|Coro::AIO> functions to save results to	1032	is when you use the L<Coro::AIO\|Coro::AIO> functions to save results to
585	disk, for example.	1033	disk, for example.
586		1034
587	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when	1035	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when
588	creating event callbacks that want to block.	1036	creating event callbacks that want to block.
589		1037
590	If your handler does not plan to block (e.g. simply sends a message to	1038	If your handler does not plan to block (e.g. simply sends a message to
591	another coroutine, or puts some other coroutine into the ready queue),	1039	another coro, or puts some other coro into the ready queue), there is
592	there is no reason to use C<unblock_sub>.	1040	no reason to use C<unblock_sub>.
593		1041
594	Note that you also need to use C<unblock_sub> for any other callbacks that	1042	Note that you also need to use C<unblock_sub> for any other callbacks that
595	are indirectly executed by any C-based event loop. For example, when you	1043	are indirectly executed by any C-based event loop. For example, when you
596	use a module that uses L<AnyEvent> (and you use L<Coro::AnyEvent>) and it	1044	use a module that uses L<AnyEvent> (and you use L<Coro::AnyEvent>) and it
597	provides callbacks that are the result of some event callback, then you	1045	provides callbacks that are the result of some event callback, then you
…		…
627	unshift @unblock_queue, [$cb, @_];	1075	unshift @unblock_queue, [$cb, @_];
628	$unblock_scheduler->ready;	1076	$unblock_scheduler->ready;
629	}	1077	}
630	}	1078	}
631		1079
632	=item $cb = Coro::rouse_cb	1080	=item $cb = rouse_cb
633		1081
634	Create and return a "rouse callback". That's a code reference that, when	1082	Create and return a "rouse callback". That's a code reference that,
635	called, will save its arguments and notify the owner coroutine of the	1083	when called, will remember a copy of its arguments and notify the owner
636	callback.	1084	coro of the callback.
637		1085
638	See the next function.	1086	See the next function.
639		1087
640	=item @args = Coro::rouse_wait [$cb]	1088	=item @args = rouse_wait [$cb]
641		1089
642	Wait for the specified rouse callback (or the last one tht was created in	1090	Wait for the specified rouse callback (or the last one that was created in
643	this coroutine).	1091	this coro).
644		1092
645	As soon as the callback is invoked (or when the calback was invoked before	1093	As soon as the callback is invoked (or when the callback was invoked
646	C<rouse_wait>), it will return a copy of the arguments originally passed	1094	before C<rouse_wait>), it will return the arguments originally passed to
647	to the rouse callback.	1095	the rouse callback. In scalar context, that means you get the I<last>
		1096	argument, just as if C<rouse_wait> had a C<return ($a1, $a2, $a3...)>
		1097	statement at the end.
648		1098
649	See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example.	1099	See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example.
650		1100
651	=back	1101	=back
652		1102
653	=cut	1103	=cut
654		1104
		1105	for my $module (qw(Channel RWLock Semaphore SemaphoreSet Signal Specific)) {
		1106	my $old = defined &{"Coro::$module\::new"} && \&{"Coro::$module\::new"};
		1107
		1108	*{"Coro::$module\::new"} = sub {
		1109	require "Coro/$module.pm";
		1110
		1111	# some modules have their new predefined in State.xs, some don't
		1112	*{"Coro::$module\::new"} = $old
		1113	if $old;
		1114
		1115	goto &{"Coro::$module\::new"};
		1116	};
		1117	}
		1118
655	1;	1119	1;
656		1120
657	=head1 HOW TO WAIT FOR A CALLBACK	1121	=head1 HOW TO WAIT FOR A CALLBACK
658		1122
659	It is very common for a coroutine to wait for some callback to be	1123	It is very common for a coro to wait for some callback to be
660	called. This occurs naturally when you use coroutines in an otherwise	1124	called. This occurs naturally when you use coro in an otherwise
661	event-based program, or when you use event-based libraries.	1125	event-based program, or when you use event-based libraries.
662		1126
663	These typically register a callback for some event, and call that callback	1127	These typically register a callback for some event, and call that callback
664	when the event occured. In a coroutine, however, you typically want to	1128	when the event occurred. In a coro, however, you typically want to
665	just wait for the event, simplyifying things.	1129	just wait for the event, simplyifying things.
666		1130
667	For example C<< AnyEvent->child >> registers a callback to be called when	1131	For example C<< AnyEvent->child >> registers a callback to be called when
668	a specific child has exited:	1132	a specific child has exited:
669		1133
670	my $child_watcher = AnyEvent->child (pid => $pid, cb => sub { ... });	1134	my $child_watcher = AnyEvent->child (pid => $pid, cb => sub { ... });
671		1135
672	But from withina coroutine, you often just want to write this:	1136	But from within a coro, you often just want to write this:
673		1137
674	my $status = wait_for_child $pid;	1138	my $status = wait_for_child $pid;
675		1139
676	Coro offers two functions specifically designed to make this easy,	1140	Coro offers two functions specifically designed to make this easy,
677	C<Coro::rouse_cb> and C<Coro::rouse_wait>.	1141	C<rouse_cb> and C<rouse_wait>.
678		1142
679	The first function, C<rouse_cb>, generates and returns a callback that,	1143	The first function, C<rouse_cb>, generates and returns a callback that,
680	when invoked, will save it's arguments and notify the coroutine that	1144	when invoked, will save its arguments and notify the coro that
681	created the callback.	1145	created the callback.
682		1146
683	The second function, C<rouse_wait>, waits for the callback to be called	1147	The second function, C<rouse_wait>, waits for the callback to be called
684	(by calling C<schedule> to go to sleep) and returns the arguments	1148	(by calling C<schedule> to go to sleep) and returns the arguments
685	originally passed to the callback.	1149	originally passed to the callback.
…		…
688	function mentioned above:	1152	function mentioned above:
689		1153
690	sub wait_for_child($) {	1154	sub wait_for_child($) {
691	my ($pid) = @_;	1155	my ($pid) = @_;
692		1156
693	my $watcher = AnyEvent->child (pid => $pid, cb => Coro::rouse_cb);	1157	my $watcher = AnyEvent->child (pid => $pid, cb => rouse_cb);
694		1158
695	my ($rpid, $rstatus) = Coro::rouse_wait;	1159	my ($rpid, $rstatus) = rouse_wait;
696	$rstatus	1160	$rstatus
697	}	1161	}
698		1162
699	In the case where C<rouse_cb> and C<rouse_wait> are not flexible enough,	1163	In the case where C<rouse_cb> and C<rouse_wait> are not flexible enough,
700	you can roll your own, using C<schedule>:	1164	you can roll your own, using C<schedule> and C<ready>:
701		1165
702	sub wait_for_child($) {	1166	sub wait_for_child($) {
703	my ($pid) = @_;	1167	my ($pid) = @_;
704		1168
705	# store the current coroutine in $current,	1169	# store the current coro in $current,
706	# and provide result variables for the closure passed to ->child	1170	# and provide result variables for the closure passed to ->child
707	my $current = $Coro::current;	1171	my $current = $Coro::current;
708	my ($done, $rstatus);	1172	my ($done, $rstatus);
709		1173
710	# pass a closure to ->child	1174	# pass a closure to ->child
711	my $watcher = AnyEvent->child (pid => $pid, cb => sub {	1175	my $watcher = AnyEvent->child (pid => $pid, cb => sub {
712	$rstatus = $_[1]; # remember rstatus	1176	$rstatus = $_[1]; # remember rstatus
713	$done = 1; # mark $rstatus as valud	1177	$done = 1; # mark $rstatus as valid
		1178	$current->ready; # wake up the waiting thread
714	});	1179	});
715		1180
716	# wait until the closure has been called	1181	# wait until the closure has been called
717	schedule while !$done;	1182	schedule while !$done;
718		1183
…		…
726		1191
727	=item fork with pthread backend	1192	=item fork with pthread backend
728		1193
729	When Coro is compiled using the pthread backend (which isn't recommended	1194	When Coro is compiled using the pthread backend (which isn't recommended
730	but required on many BSDs as their libcs are completely broken), then	1195	but required on many BSDs as their libcs are completely broken), then
731	coroutines will not survive a fork. There is no known workaround except to	1196	coro will not survive a fork. There is no known workaround except to
732	fix your libc and use a saner backend.	1197	fix your libc and use a saner backend.
733		1198
734	=item perl process emulation ("threads")	1199	=item perl process emulation ("threads")
735		1200
736	This module is not perl-pseudo-thread-safe. You should only ever use this	1201	This module is not perl-pseudo-thread-safe. You should only ever use this
737	module from the same thread (this requirement might be removed in the	1202	module from the first thread (this requirement might be removed in the
738	future to allow per-thread schedulers, but Coro::State does not yet allow	1203	future to allow per-thread schedulers, but Coro::State does not yet allow
739	this). I recommend disabling thread support and using processes, as having	1204	this). I recommend disabling thread support and using processes, as having
740	the windows process emulation enabled under unix roughly halves perl	1205	the windows process emulation enabled under unix roughly halves perl
741	performance, even when not used.	1206	performance, even when not used.
742		1207
		1208	Attempts to use threads created in another emulated process will crash
		1209	("cleanly", with a null pointer exception).
		1210
743	=item coroutine switching not signal safe	1211	=item coro switching is not signal safe
744		1212
745	You must not switch to another coroutine from within a signal handler	1213	You must not switch to another coro from within a signal handler (only
746	(only relevant with %SIG - most event libraries provide safe signals).	1214	relevant with %SIG - most event libraries provide safe signals), I<unless>
		1215	you are sure you are not interrupting a Coro function.
747		1216
748	That means you I<MUST NOT> call any function that might "block" the	1217	That means you I<MUST NOT> call any function that might "block" the
749	current coroutine - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or	1218	current coro - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or
750	anything that calls those. Everything else, including calling C<ready>,	1219	anything that calls those. Everything else, including calling C<ready>,
751	works.	1220	works.
752		1221
753	=back	1222	=back
754		1223
755		1224
		1225	=head1 WINDOWS PROCESS EMULATION
		1226
		1227	A great many people seem to be confused about ithreads (for example, Chip
		1228	Salzenberg called me unintelligent, incapable, stupid and gullible,
		1229	while in the same mail making rather confused statements about perl
		1230	ithreads (for example, that memory or files would be shared), showing his
		1231	lack of understanding of this area - if it is hard to understand for Chip,
		1232	it is probably not obvious to everybody).
		1233
		1234	What follows is an ultra-condensed version of my talk about threads in
		1235	scripting languages given on the perl workshop 2009:
		1236
		1237	The so-called "ithreads" were originally implemented for two reasons:
		1238	first, to (badly) emulate unix processes on native win32 perls, and
		1239	secondly, to replace the older, real thread model ("5.005-threads").
		1240
		1241	It does that by using threads instead of OS processes. The difference
		1242	between processes and threads is that threads share memory (and other
		1243	state, such as files) between threads within a single process, while
		1244	processes do not share anything (at least not semantically). That
		1245	means that modifications done by one thread are seen by others, while
		1246	modifications by one process are not seen by other processes.
		1247
		1248	The "ithreads" work exactly like that: when creating a new ithreads
		1249	process, all state is copied (memory is copied physically, files and code
		1250	is copied logically). Afterwards, it isolates all modifications. On UNIX,
		1251	the same behaviour can be achieved by using operating system processes,
		1252	except that UNIX typically uses hardware built into the system to do this
		1253	efficiently, while the windows process emulation emulates this hardware in
		1254	software (rather efficiently, but of course it is still much slower than
		1255	dedicated hardware).
		1256
		1257	As mentioned before, loading code, modifying code, modifying data
		1258	structures and so on is only visible in the ithreads process doing the
		1259	modification, not in other ithread processes within the same OS process.
		1260
		1261	This is why "ithreads" do not implement threads for perl at all, only
		1262	processes. What makes it so bad is that on non-windows platforms, you can
		1263	actually take advantage of custom hardware for this purpose (as evidenced
		1264	by the forks module, which gives you the (i-) threads API, just much
		1265	faster).
		1266
		1267	Sharing data is in the i-threads model is done by transferring data
		1268	structures between threads using copying semantics, which is very slow -
		1269	shared data simply does not exist. Benchmarks using i-threads which are
		1270	communication-intensive show extremely bad behaviour with i-threads (in
		1271	fact, so bad that Coro, which cannot take direct advantage of multiple
		1272	CPUs, is often orders of magnitude faster because it shares data using
		1273	real threads, refer to my talk for details).
		1274
		1275	As summary, i-threads use threads to implement processes, while
		1276	the compatible forks module uses processes to emulate, uhm,
		1277	processes. I-threads slow down every perl program when enabled, and
		1278	outside of windows, serve no (or little) practical purpose, but
		1279	disadvantages every single-threaded Perl program.
		1280
		1281	This is the reason that I try to avoid the name "ithreads", as it is
		1282	misleading as it implies that it implements some kind of thread model for
		1283	perl, and prefer the name "windows process emulation", which describes the
		1284	actual use and behaviour of it much better.
		1285
756	=head1 SEE ALSO	1286	=head1 SEE ALSO
757		1287
758	Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.	1288	Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
759		1289
760	Debugging: L<Coro::Debug>.	1290	Debugging: L<Coro::Debug>.
761		1291
762	Support/Utility: L<Coro::Specific>, L<Coro::Util>.	1292	Support/Utility: L<Coro::Specific>, L<Coro::Util>.
763		1293
764	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>,	1294	Locking and IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>,
765	L<Coro::SemaphoreSet>, L<Coro::RWLock>.	1295	L<Coro::SemaphoreSet>, L<Coro::RWLock>.
766		1296
767	IO/Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>.	1297	I/O and Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>.
768		1298
769	Compatibility: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for	1299	Compatibility with other modules: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for
770	a better-working alternative), L<Coro::BDB>, L<Coro::Storable>,	1300	a better-working alternative), L<Coro::BDB>, L<Coro::Storable>,
771	L<Coro::Select>.	1301	L<Coro::Select>.
772		1302
773	XS API: L<Coro::MakeMaker>.	1303	XS API: L<Coro::MakeMaker>.
774		1304
775	Low level Configuration, Coroutine Environment: L<Coro::State>.	1305	Low level Configuration, Thread Environment, Continuations: L<Coro::State>.
776		1306
777	=head1 AUTHOR	1307	=head1 AUTHOR/SUPPORT/CONTACT
778		1308
779	Marc Lehmann <schmorp@schmorp.de>	1309	Marc A. Lehmann <schmorp@schmorp.de>
780	http://home.schmorp.de/	1310	http://software.schmorp.de/pkg/Coro.html
781		1311
782	=cut	1312	=cut
783		1313

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.237 by root, Sat Nov 22 16:37:11 2008 UTC vs. Revision 1.346 by root, Fri Jul 14 23:20:07 2017 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.237 by root, Sat Nov 22 16:37:11 2008 UTC vs.
Revision 1.346 by root, Fri Jul 14 23:20:07 2017 UTC