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

Comparing Coro/Coro.pm (file contents):
Revision 1.280 by root, Thu Nov 11 15:07:16 2010 UTC vs.
Revision 1.321 by root, Sun Feb 2 03:26:06 2014 UTC

…		…
16	cede; # yield to coro	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;
…		…
40	points in your program, so locking and parallel access are rarely an	39	points in your program, so locking and parallel access are rarely an
41	issue, making thread programming much safer and easier than using other	40	issue, making thread programming much safer and easier than using other
42	thread models.	41	thread models.
43		42
44	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
45	but only the windows process emulation (see section of same name for more	44	but only the windows process emulation (see section of same name for
46	details) ported to unix, and as such act as processes), Coro provides	45	more details) ported to UNIX, and as such act as processes), Coro
47	a full shared address space, which makes communication between threads	46	provides a full shared address space, which makes communication between
48	very easy. And Coro's threads are fast, too: disabling the Windows	47	threads very easy. And coro threads are fast, too: disabling the Windows
49	process emulation code in your perl and using Coro can easily result in	48	process emulation code in your perl and using Coro can easily result in
50	a two to four times speed increase for your programs. A parallel matrix	49	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	50	multiplication benchmark (very communication-intensive) runs over 300
52	perl's pseudo-threads on a quad core using all four cores.	51	times faster on a single core than perls pseudo-threads on a quad core
		52	using all four cores.
53		53
54	Coro achieves that by supporting multiple running interpreters that share	54	Coro achieves that by supporting multiple running interpreters that share
55	data, which is especially useful to code pseudo-parallel processes and	55	data, which is especially useful to code pseudo-parallel processes and
56	for event-based programming, such as multiple HTTP-GET requests running	56	for event-based programming, such as multiple HTTP-GET requests running
57	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
…		…
63	variables (see L<Coro::State> for more configuration and background info).	63	variables (see L<Coro::State> for more configuration and background info).
64		64
65	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
66	module family is quite large.	66	module family is quite large.
67		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
68	=cut	353	=cut
69		354
70	package Coro;	355	package Coro;
71		356
72	use common::sense;	357	use common::sense;
…		…
81		366
82	our $idle; # idle handler	367	our $idle; # idle handler
83	our $main; # main coro	368	our $main; # main coro
84	our $current; # current coro	369	our $current; # current coro
85		370
86	our $VERSION = 5.25;	371	our $VERSION = 6.33;
87		372
88	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait);	373	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait);
89	our %EXPORT_TAGS = (	374	our %EXPORT_TAGS = (
90	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)],
91	);	376	);
…		…
96	=over 4	381	=over 4
97		382
98	=item $Coro::main	383	=item $Coro::main
99		384
100	This variable stores the Coro object that represents the main	385	This variable stores the Coro object that represents the main
101	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
102	coro, 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
103	whether you are running in the main program or not.	388	whether you are running in the main program or not.
104		389
105	=cut	390	=cut
106		391
…		…
131		416
132	The default implementation dies with "FATAL: deadlock detected.", followed	417	The default implementation dies with "FATAL: deadlock detected.", followed
133	by a thread listing, because the program has no other way to continue.	418	by a thread listing, because the program has no other way to continue.
134		419
135	This hook is overwritten by modules such as C<Coro::EV> and	420	This hook is overwritten by modules such as C<Coro::EV> and
136	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
137	coro so the scheduler can run it.	422	coro so the scheduler can run it.
138		423
139	See L<Coro::EV> or L<Coro::AnyEvent> for examples of using this technique.	424	See L<Coro::EV> or L<Coro::AnyEvent> for examples of using this technique.
140		425
141	=cut	426	=cut
…		…
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::State::cancel shift @destroy	442	_destroy shift @destroy
158	while @destroy;	443	while @destroy;
159		444
160	&schedule;	445	&schedule;
161	}	446	}
162	};	447	};
…		…
296	coro, regardless of priority. This is useful sometimes to ensure	581	coro, regardless of priority. This is useful sometimes to ensure
297	progress is made.	582	progress is made.
298		583
299	=item terminate [arg...]	584	=item terminate [arg...]
300		585
301	Terminates the current coro with the given status values (see L<cancel>).	586	Terminates the current coro with the given status values (see
		587	L<cancel>). The values will not be copied, but referenced directly.
302		588
303	=item Coro::on_enter BLOCK, Coro::on_leave BLOCK	589	=item Coro::on_enter BLOCK, Coro::on_leave BLOCK
304		590
305	These function install enter and leave winders in the current scope. The	591	These function install enter and leave winders in the current scope. The
306	enter block will be executed when on_enter is called and whenever the	592	enter block will be executed when on_enter is called and whenever the
…		…
462	To avoid this, it is best to put a suspended coro into the ready queue	748	To avoid this, it is best to put a suspended coro into the ready queue
463	unconditionally, as every synchronisation mechanism must protect itself	749	unconditionally, as every synchronisation mechanism must protect itself
464	against spurious wakeups, and the one in the Coro family certainly do	750	against spurious wakeups, and the one in the Coro family certainly do
465	that.	751	that.
466		752
		753	=item $state->is_new
		754
		755	Returns true iff this Coro object is "new", i.e. has never been run
		756	yet. Those states basically consist of only the code reference to call and
		757	the arguments, but consumes very little other resources. New states will
		758	automatically get assigned a perl interpreter when they are transfered to.
		759
		760	=item $state->is_zombie
		761
		762	Returns true iff the Coro object has been cancelled, i.e.
		763	it's resources freed because they were C<cancel>'ed, C<terminate>'d,
		764	C<safe_cancel>'ed or simply went out of scope.
		765
		766	The name "zombie" stems from UNIX culture, where a process that has
		767	exited and only stores and exit status and no other resources is called a
		768	"zombie".
		769
467	=item $is_ready = $coro->is_ready	770	=item $is_ready = $coro->is_ready
468		771
469	Returns true iff the Coro object is in the ready queue. Unless the Coro	772	Returns true iff the Coro object is in the ready queue. Unless the Coro
470	object gets destroyed, it will eventually be scheduled by the scheduler.	773	object gets destroyed, it will eventually be scheduled by the scheduler.
471		774
…		…
480	Returns true iff this Coro object has been suspended. Suspended Coros will	783	Returns true iff this Coro object has been suspended. Suspended Coros will
481	not ever be scheduled.	784	not ever be scheduled.
482		785
483	=item $coro->cancel (arg...)	786	=item $coro->cancel (arg...)
484		787
485	Terminates the given Coro and makes it return the given arguments as	788	Terminates the given Coro thread and makes it return the given arguments as
486	status (default: the empty list). Never returns if the Coro is the	789	status (default: an empty list). Never returns if the Coro is the
487	current Coro.	790	current Coro.
488		791
489	=cut	792	This is a rather brutal way to free a coro, with some limitations - if
		793	the thread is inside a C callback that doesn't expect to be canceled,
		794	bad things can happen, or if the cancelled thread insists on running
		795	complicated cleanup handlers that rely on its thread context, things will
		796	not work.
490		797
491	sub cancel {	798	Any cleanup code being run (e.g. from C<guard> blocks) will be run without
492	my $self = shift;	799	a thread context, and is not allowed to switch to other threads. On the
		800	plus side, C<< ->cancel >> will always clean up the thread, no matter
		801	what. If your cleanup code is complex or you want to avoid cancelling a
		802	C-thread that doesn't know how to clean up itself, it can be better to C<<
		803	->throw >> an exception, or use C<< ->safe_cancel >>.
493		804
494	if ($current == $self) {	805	The arguments to C<< ->cancel >> are not copied, but instead will
495	terminate @_;	806	be referenced directly (e.g. if you pass C<$var> and after the call
496	} else {	807	change that variable, then you might change the return values passed to
497	$self->{_status} = [@_];	808	e.g. C<join>, so don't do that).
498	Coro::State::cancel $self;	809
		810	The resources of the Coro are usually freed (or destructed) before this
		811	call returns, but this can be delayed for an indefinite amount of time, as
		812	in some cases the manager thread has to run first to actually destruct the
		813	Coro object.
		814
		815	=item $coro->safe_cancel ($arg...)
		816
		817	Works mostly like C<< ->cancel >>, but is inherently "safer", and
		818	consequently, can fail with an exception in cases the thread is not in a
		819	cancellable state.
		820
		821	This method works a bit like throwing an exception that cannot be caught
		822	- specifically, it will clean up the thread from within itself, so
		823	all cleanup handlers (e.g. C<guard> blocks) are run with full thread
		824	context and can block if they wish. The downside is that there is no
		825	guarantee that the thread can be cancelled when you call this method, and
		826	therefore, it might fail. It is also considerably slower than C<cancel> or
		827	C<terminate>.
		828
		829	A thread is in a safe-cancellable state if it either hasn't been run yet,
		830	or it has no C context attached and is inside an SLF function.
		831
		832	The latter two basically mean that the thread isn't currently inside a
		833	perl callback called from some C function (usually via some XS modules)
		834	and isn't currently executing inside some C function itself (via Coro's XS
		835	API).
		836
		837	This call returns true when it could cancel the thread, or croaks with an
		838	error otherwise (i.e. it either returns true or doesn't return at all).
		839
		840	Why the weird interface? Well, there are two common models on how and
		841	when to cancel things. In the first, you have the expectation that your
		842	coro thread can be cancelled when you want to cancel it - if the thread
		843	isn't cancellable, this would be a bug somewhere, so C<< ->safe_cancel >>
		844	croaks to notify of the bug.
		845
		846	In the second model you sometimes want to ask nicely to cancel a thread,
		847	but if it's not a good time, well, then don't cancel. This can be done
		848	relatively easy like this:
		849
		850	if (! eval { $coro->safe_cancel }) {
		851	warn "unable to cancel thread: $@";
499	}	852	}
500	}	853
		854	However, what you never should do is first try to cancel "safely" and
		855	if that fails, cancel the "hard" way with C<< ->cancel >>. That makes
		856	no sense: either you rely on being able to execute cleanup code in your
		857	thread context, or you don't. If you do, then C<< ->safe_cancel >> is the
		858	only way, and if you don't, then C<< ->cancel >> is always faster and more
		859	direct.
501		860
502	=item $coro->schedule_to	861	=item $coro->schedule_to
503		862
504	Puts the current coro to sleep (like C<Coro::schedule>), but instead	863	Puts the current coro to sleep (like C<Coro::schedule>), but instead
505	of continuing with the next coro from the ready queue, always switch to	864	of continuing with the next coro from the ready queue, always switch to
…		…
524	inside the coro at the next convenient point in time. Otherwise	883	inside the coro at the next convenient point in time. Otherwise
525	clears the exception object.	884	clears the exception object.
526		885
527	Coro will check for the exception each time a schedule-like-function	886	Coro will check for the exception each time a schedule-like-function
528	returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down	887	returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down
529	>>, C<< Coro::Handle->readable >> and so on. Most of these functions	888	>>, C<< Coro::Handle->readable >> and so on. Most of those functions (all
530	detect this case and return early in case an exception is pending.	889	that are part of Coro itself) detect this case and return early in case an
		890	exception is pending.
531		891
532	The exception object will be thrown "as is" with the specified scalar in	892	The exception object will be thrown "as is" with the specified scalar in
533	C<$@>, i.e. if it is a string, no line number or newline will be appended	893	C<$@>, i.e. if it is a string, no line number or newline will be appended
534	(unlike with C<die>).	894	(unlike with C<die>).
535		895
536	This can be used as a softer means than C<cancel> to ask a coro to	896	This can be used as a softer means than either C<cancel> or C<safe_cancel
537	end itself, although there is no guarantee that the exception will lead to	897	>to ask a coro to end itself, although there is no guarantee that the
538	termination, and if the exception isn't caught it might well end the whole	898	exception will lead to termination, and if the exception isn't caught it
539	program.	899	might well end the whole program.
540		900
541	You might also think of C<throw> as being the moral equivalent of	901	You might also think of C<throw> as being the moral equivalent of
542	C<kill>ing a coro with a signal (in this case, a scalar).	902	C<kill>ing a coro with a signal (in this case, a scalar).
543		903
544	=item $coro->join	904	=item $coro->join
545		905
546	Wait until the coro terminates and return any values given to the	906	Wait until the coro terminates and return any values given to the
547	C<terminate> or C<cancel> functions. C<join> can be called concurrently	907	C<terminate> or C<cancel> functions. C<join> can be called concurrently
548	from multiple coro, and all will be resumed and given the status	908	from multiple threads, and all will be resumed and given the status
549	return once the C<$coro> terminates.	909	return once the C<$coro> terminates.
550		910
551	=cut
552
553	sub join {
554	my $self = shift;
555
556	unless ($self->{_status}) {
557	my $current = $current;
558
559	push @{$self->{_on_destroy}}, sub {
560	$current->ready;
561	undef $current;
562	};
563
564	&schedule while $current;
565	}
566
567	wantarray ? @{$self->{_status}} : $self->{_status}[0];
568	}
569
570	=item $coro->on_destroy (\&cb)	911	=item $coro->on_destroy (\&cb)
571		912
572	Registers a callback that is called when this coro gets destroyed,	913	Registers a callback that is called when this coro thread gets destroyed,
573	but before it is joined. The callback gets passed the terminate arguments,	914	that is, after it's resources have been freed but before it is joined. The
		915	callback gets passed the terminate/cancel arguments, if any, and I<must
574	if any, and I<must not> die, under any circumstances.	916	not> die, under any circumstances.
575		917
576	=cut	918	There can be any number of C<on_destroy> callbacks per coro, and there is
577		919	currently no way to remove a callback once added.
578	sub on_destroy {
579	my ($self, $cb) = @_;
580
581	push @{ $self->{_on_destroy} }, $cb;
582	}
583		920
584	=item $oldprio = $coro->prio ($newprio)	921	=item $oldprio = $coro->prio ($newprio)
585		922
586	Sets (or gets, if the argument is missing) the priority of the	923	Sets (or gets, if the argument is missing) the priority of the
587	coro. Higher priority coro get run before lower priority	924	coro thread. Higher priority coro get run before lower priority
588	coro. Priorities are small signed integers (currently -4 .. +3),	925	coros. Priorities are small signed integers (currently -4 .. +3),
589	that you can refer to using PRIO_xxx constants (use the import tag :prio	926	that you can refer to using PRIO_xxx constants (use the import tag :prio
590	to get then):	927	to get then):
591		928
592	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN	929	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
593	3 > 1 > 0 > -1 > -3 > -4	930	3 > 1 > 0 > -1 > -3 > -4
594		931
595	# set priority to HIGH	932	# set priority to HIGH
596	current->prio (PRIO_HIGH);	933	current->prio (PRIO_HIGH);
597		934
598	The idle coro ($Coro::idle) always has a lower priority than any	935	The idle coro thread ($Coro::idle) always has a lower priority than any
599	existing coro.	936	existing coro.
600		937
601	Changing the priority of the current coro will take effect immediately,	938	Changing the priority of the current coro will take effect immediately,
602	but changing the priority of coro in the ready queue (but not	939	but changing the priority of a coro in the ready queue (but not running)
603	running) will only take effect after the next schedule (of that	940	will only take effect after the next schedule (of that coro). This is a
604	coro). This is a bug that will be fixed in some future version.	941	bug that will be fixed in some future version.
605		942
606	=item $newprio = $coro->nice ($change)	943	=item $newprio = $coro->nice ($change)
607		944
608	Similar to C<prio>, but subtract the given value from the priority (i.e.	945	Similar to C<prio>, but subtract the given value from the priority (i.e.
609	higher values mean lower priority, just as in unix).	946	higher values mean lower priority, just as in UNIX's nice command).
610		947
611	=item $olddesc = $coro->desc ($newdesc)	948	=item $olddesc = $coro->desc ($newdesc)
612		949
613	Sets (or gets in case the argument is missing) the description for this	950	Sets (or gets in case the argument is missing) the description for this
614	coro. This is just a free-form string you can associate with a	951	coro thread. This is just a free-form string you can associate with a
615	coro.	952	coro.
616		953
617	This method simply sets the C<< $coro->{desc} >> member to the given	954	This method simply sets the C<< $coro->{desc} >> member to the given
618	string. You can modify this member directly if you wish, and in fact, this	955	string. You can modify this member directly if you wish, and in fact, this
619	is often preferred to indicate major processing states that cna then be	956	is often preferred to indicate major processing states that can then be
620	seen for example in a L<Coro::Debug> session:	957	seen for example in a L<Coro::Debug> session:
621		958
622	sub my_long_function {	959	sub my_long_function {
623	local $Coro::current->{desc} = "now in my_long_function";	960	local $Coro::current->{desc} = "now in my_long_function";
624	...	961	...
…		…
671	returning a new coderef. Unblocking means that calling the new coderef	1008	returning a new coderef. Unblocking means that calling the new coderef
672	will return immediately without blocking, returning nothing, while the	1009	will return immediately without blocking, returning nothing, while the
673	original code ref will be called (with parameters) from within another	1010	original code ref will be called (with parameters) from within another
674	coro.	1011	coro.
675		1012
676	The reason this function exists is that many event libraries (such as the	1013	The reason this function exists is that many event libraries (such as
677	venerable L<Event\|Event> module) are not thread-safe (a weaker form	1014	the venerable L<Event\|Event> module) are not thread-safe (a weaker form
678	of reentrancy). This means you must not block within event callbacks,	1015	of reentrancy). This means you must not block within event callbacks,
679	otherwise you might suffer from crashes or worse. The only event library	1016	otherwise you might suffer from crashes or worse. The only event library
680	currently known that is safe to use without C<unblock_sub> is L<EV>.	1017	currently known that is safe to use without C<unblock_sub> is L<EV> (but
		1018	you might still run into deadlocks if all event loops are blocked).
681		1019
682	Coro will try to catch you when you block in the event loop	1020	Coro will try to catch you when you block in the event loop
683	("FATAL:$Coro::IDLE blocked itself"), but this is just best effort and	1021	("FATAL:$Coro::IDLE blocked itself"), but this is just best effort and
684	only works when you do not run your own event loop.	1022	only works when you do not run your own event loop.
685		1023
…		…
756		1094
757	=back	1095	=back
758		1096
759	=cut	1097	=cut
760		1098
		1099	for my $module (qw(Channel RWLock Semaphore SemaphoreSet Signal Specific)) {
		1100	my $old = defined &{"Coro::$module\::new"} && \&{"Coro::$module\::new"};
		1101
		1102	*{"Coro::$module\::new"} = sub {
		1103	require "Coro/$module.pm";
		1104
		1105	# some modules have their new predefined in State.xs, some don't
		1106	*{"Coro::$module\::new"} = $old
		1107	if $old;
		1108
		1109	goto &{"Coro::$module\::new"};
		1110	};
		1111	}
		1112
761	1;	1113	1;
762		1114
763	=head1 HOW TO WAIT FOR A CALLBACK	1115	=head1 HOW TO WAIT FOR A CALLBACK
764		1116
765	It is very common for a coro to wait for some callback to be	1117	It is very common for a coro to wait for some callback to be
…		…
778	But from within a coro, you often just want to write this:	1130	But from within a coro, you often just want to write this:
779		1131
780	my $status = wait_for_child $pid;	1132	my $status = wait_for_child $pid;
781		1133
782	Coro offers two functions specifically designed to make this easy,	1134	Coro offers two functions specifically designed to make this easy,
783	C<Coro::rouse_cb> and C<Coro::rouse_wait>.	1135	C<rouse_cb> and C<rouse_wait>.
784		1136
785	The first function, C<rouse_cb>, generates and returns a callback that,	1137	The first function, C<rouse_cb>, generates and returns a callback that,
786	when invoked, will save its arguments and notify the coro that	1138	when invoked, will save its arguments and notify the coro that
787	created the callback.	1139	created the callback.
788		1140
…		…
794	function mentioned above:	1146	function mentioned above:
795		1147
796	sub wait_for_child($) {	1148	sub wait_for_child($) {
797	my ($pid) = @_;	1149	my ($pid) = @_;
798		1150
799	my $watcher = AnyEvent->child (pid => $pid, cb => Coro::rouse_cb);	1151	my $watcher = AnyEvent->child (pid => $pid, cb => rouse_cb);
800		1152
801	my ($rpid, $rstatus) = Coro::rouse_wait;	1153	my ($rpid, $rstatus) = rouse_wait;
802	$rstatus	1154	$rstatus
803	}	1155	}
804		1156
805	In the case where C<rouse_cb> and C<rouse_wait> are not flexible enough,	1157	In the case where C<rouse_cb> and C<rouse_wait> are not flexible enough,
806	you can roll your own, using C<schedule>:	1158	you can roll your own, using C<schedule> and C<ready>:
807		1159
808	sub wait_for_child($) {	1160	sub wait_for_child($) {
809	my ($pid) = @_;	1161	my ($pid) = @_;
810		1162
811	# store the current coro in $current,	1163	# store the current coro in $current,
…		…
814	my ($done, $rstatus);	1166	my ($done, $rstatus);
815		1167
816	# pass a closure to ->child	1168	# pass a closure to ->child
817	my $watcher = AnyEvent->child (pid => $pid, cb => sub {	1169	my $watcher = AnyEvent->child (pid => $pid, cb => sub {
818	$rstatus = $_[1]; # remember rstatus	1170	$rstatus = $_[1]; # remember rstatus
819	$done = 1; # mark $rstatus as valud	1171	$done = 1; # mark $rstatus as valid
		1172	$current->ready; # wake up the waiting thread
820	});	1173	});
821		1174
822	# wait until the closure has been called	1175	# wait until the closure has been called
823	schedule while !$done;	1176	schedule while !$done;
824		1177
…		…
844	future to allow per-thread schedulers, but Coro::State does not yet allow	1197	future to allow per-thread schedulers, but Coro::State does not yet allow
845	this). I recommend disabling thread support and using processes, as having	1198	this). I recommend disabling thread support and using processes, as having
846	the windows process emulation enabled under unix roughly halves perl	1199	the windows process emulation enabled under unix roughly halves perl
847	performance, even when not used.	1200	performance, even when not used.
848		1201
		1202	Attempts to use threads created in another emulated process will crash
		1203	("cleanly", with a null pointer exception).
		1204
849	=item coro switching is not signal safe	1205	=item coro switching is not signal safe
850		1206
851	You must not switch to another coro from within a signal handler (only	1207	You must not switch to another coro from within a signal handler (only
852	relevant with %SIG - most event libraries provide safe signals), I<unless>	1208	relevant with %SIG - most event libraries provide safe signals), I<unless>
853	you are sure you are not interrupting a Coro function.	1209	you are sure you are not interrupting a Coro function.
…		…
868	ithreads (for example, that memory or files would be shared), showing his	1224	ithreads (for example, that memory or files would be shared), showing his
869	lack of understanding of this area - if it is hard to understand for Chip,	1225	lack of understanding of this area - if it is hard to understand for Chip,
870	it is probably not obvious to everybody).	1226	it is probably not obvious to everybody).
871		1227
872	What follows is an ultra-condensed version of my talk about threads in	1228	What follows is an ultra-condensed version of my talk about threads in
873	scripting languages given onthe perl workshop 2009:	1229	scripting languages given on the perl workshop 2009:
874		1230
875	The so-called "ithreads" were originally implemented for two reasons:	1231	The so-called "ithreads" were originally implemented for two reasons:
876	first, to (badly) emulate unix processes on native win32 perls, and	1232	first, to (badly) emulate unix processes on native win32 perls, and
877	secondly, to replace the older, real thread model ("5.005-threads").	1233	secondly, to replace the older, real thread model ("5.005-threads").
878		1234

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.280 by root, Thu Nov 11 15:07:16 2010 UTC vs. Revision 1.321 by root, Sun Feb 2 03:26:06 2014 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.280 by root, Thu Nov 11 15:07:16 2010 UTC vs.
Revision 1.321 by root, Sun Feb 2 03:26:06 2014 UTC