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

Comparing Coro/Coro.pm (file contents):
Revision 1.7 by root, Fri Jul 13 13:05:38 2001 UTC vs.
Revision 1.245 by root, Sun Dec 14 19:52:58 2008 UTC

1	=head1 NAME	1	=head1 NAME
2		2
3	Coro - create and manage simple coroutines	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
9	$new = new Coro sub {	9	async {
10	print "in coroutine, switching back\n";	10	# some asynchronous thread of execution
11	$new->transfer($main);	11	print "2\n";
12	print "in coroutine again, switching back\n";	12	cede; # yield back to main
13	$new->transfer($main);	13	print "4\n";
14	};	14	};
15		15	print "1\n";
16	$main = new Coro;	16	cede; # yield to coroutine
17		17	print "3\n";
18	print "in main, switching to coroutine\n";	18	cede; # and again
19	$main->transfer($new);	19
20	print "back in main, switch to coroutine again\n";	20	# use locking
21	$main->transfer($new);	21	use Coro::Semaphore;
22	print "back in main\n";	22	my $lock = new Coro::Semaphore;
		23	my $locked;
		24
		25	$lock->down;
		26	$locked = 1;
		27	$lock->up;
23		28
24	=head1 DESCRIPTION	29	=head1 DESCRIPTION
25		30
26	This module implements coroutines. Coroutines, similar to continuations,	31	For a tutorial-style introduction, please read the L<Coro::Intro>
27	allow you to run more than one "thread of execution" in parallel. Unlike	32	manpage. This manpage mainly contains reference information.
28	threads this, only voluntary switching is used so locking problems are
29	greatly reduced.
30		33
31	Although this is the "main" module of the Coro family it provides only	34	This module collection manages continuations in general, most often
32	low-level functionality. See L<Coro::Process> and related modules for a	35	in the form of cooperative threads (also called coroutines in the
33	more useful process abstraction including scheduling.	36	documentation). They are similar to kernel threads but don't (in general)
		37	run in parallel at the same time even on SMP machines. The specific flavor
		38	of thread offered by this module also guarantees you that it will not
		39	switch between threads unless necessary, at easily-identified points in
		40	your program, so locking and parallel access are rarely an issue, making
		41	thread programming much safer and easier than using other thread models.
		42
		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
		45	full shared address space, which makes communication between threads
		46	very easy. And threads are fast, too: disabling the Windows process
		47	emulation code in your perl and using Coro can easily result in a two to
		48	four times speed increase for your programs.
		49
		50	Coro achieves that by supporting multiple running interpreters that share
		51	data, which is especially useful to code pseudo-parallel processes and
		52	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
		54	into an event-based environment.
		55
		56	In this module, a thread is defined as "callchain + lexical variables +
		57	@_ + $_ + $@ + $/ + C stack), that is, a thread has its own callchain,
		58	its own set of lexicals and its own set of perls most important global
		59	variables (see L<Coro::State> for more configuration and background info).
		60
		61	See also the C<SEE ALSO> section at the end of this document - the Coro
		62	module family is quite large.
		63
		64	=cut
		65
		66	package Coro;
		67
		68	use strict qw(vars subs);
		69	no warnings "uninitialized";
		70
		71	use Coro::State;
		72
		73	use base qw(Coro::State Exporter);
		74
		75	our $idle; # idle handler
		76	our $main; # main coroutine
		77	our $current; # current coroutine
		78
		79	our $VERSION = 5.13;
		80
		81	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
		82	our %EXPORT_TAGS = (
		83	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
		84	);
		85	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));
		86
		87	=head1 GLOBAL VARIABLES
34		88
35	=over 4	89	=over 4
36		90
37	=cut	91	=item $Coro::main
38		92
39	package Coro;	93	This variable stores the coroutine object that represents the main
		94	program. While you cna C<ready> it and do most other things you can do to
		95	coroutines, it is mainly useful to compare again C<$Coro::current>, to see
		96	whether you are running in the main program or not.
40		97
41	BEGIN {	98	=cut
42	$VERSION = 0.03;
43		99
		100	# $main is now being initialised by Coro::State
		101
		102	=item $Coro::current
		103
		104	The coroutine object representing the current coroutine (the last
		105	coroutine that the Coro scheduler switched to). The initial value is
		106	C<$Coro::main> (of course).
		107
		108	This variable is B<strictly> I<read-only>. You can take copies of the
		109	value stored in it and use it as any other coroutine object, but you must
		110	not otherwise modify the variable itself.
		111
		112	=cut
		113
		114	sub current() { $current } # [DEPRECATED]
		115
		116	=item $Coro::idle
		117
		118	This variable is mainly useful to integrate Coro into event loops. It is
		119	usually better to rely on L<Coro::AnyEvent> or L<Coro::EV>, as this is
		120	pretty low-level functionality.
		121
		122	This variable stores either a coroutine or a callback.
		123
		124	If it is a callback, the it is called whenever the scheduler finds no
		125	ready coroutines to run. The default implementation prints "FATAL:
		126	deadlock detected" and exits, because the program has no other way to
		127	continue.
		128
		129	If it is a coroutine object, then this object will be readied (without
		130	invoking any ready hooks, however) when the scheduler finds no other ready
		131	coroutines to run.
		132
		133	This hook is overwritten by modules such as C<Coro::EV> and
		134	C<Coro::AnyEvent> to wait on an external event that hopefully wake up a
		135	coroutine so the scheduler can run it.
		136
		137	Note that the callback I<must not>, under any circumstances, block
		138	the current coroutine. Normally, this is achieved by having an "idle
		139	coroutine" that calls the event loop and then blocks again, and then
		140	readying that coroutine in the idle handler, or by simply placing the idle
		141	coroutine in this variable.
		142
		143	See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this
		144	technique.
		145
		146	Please note that if your callback recursively invokes perl (e.g. for event
		147	handlers), then it must be prepared to be called recursively itself.
		148
		149	=cut
		150
		151	$idle = sub {
44	require XSLoader;	152	require Carp;
45	XSLoader::load Coro, $VERSION;	153	Carp::croak ("FATAL: deadlock detected");
46	}	154	};
47		155
48	=item $coro = new [$coderef [, @args]]	156	# this coroutine is necessary because a coroutine
		157	# cannot destroy itself.
		158	our @destroy;
		159	our $manager;
49		160
50	Create a new coroutine and return it. The first C<transfer> call to this	161	$manager = new Coro sub {
51	coroutine will start execution at the given coderef. If, the subroutine	162	while () {
52	returns it will be executed again.	163	Coro::_cancel shift @destroy
		164	while @destroy;
53		165
54	If the coderef is omitted this function will create a new "empty"	166	&schedule;
55	coroutine, i.e. a coroutine that cannot be transfered to but can be used
56	to save the current coroutine in.
57
58	=cut
59
60	sub new {
61	my $class = $_[0];
62	my $proc = $_[1] \|\| sub { die "tried to transfer to an empty coroutine" };
63	bless _newprocess {
64	do {
65	eval { &$proc };
66	if ($@) {
67	$error_msg = $@;
68	$error_coro = _newprocess { };
69	&transfer($error_coro, $error);
70	}
71	} while (1);
72	}, $class;
73	}
74
75	=item $prev->transfer($next)
76
77	Save the state of the current subroutine in C<$prev> and switch to the
78	coroutine saved in C<$next>.
79
80	The "state" of a subroutine only ever includes scope, i.e. lexical
81	variables and the current execution state. It does not save/restore any
82	global variables such as C<$_> or C<$@> or any other special or non
83	special variables. So remember that every function call that might call
84	C<transfer> (such as C<Coro::Channel::put>) might clobber any global
85	and/or special variables. Yes, this is by design ;) You cna always create
86	your own process abstraction model that saves these variables.
87
88	The easiest way to do this is to create your own scheduling primitive like this:
89
90	sub schedule {
91	local ($_, $@, ...);
92	$old->transfer($new);
93	}	167	}
		168	};
		169	$manager->{desc} = "[coro manager]";
		170	$manager->prio (PRIO_MAX);
94		171
95	=cut	172	=back
96		173
97	# I call the _transfer function from a perl function	174	=head1 SIMPLE COROUTINE CREATION
98	# because that way perl saves all important things on	175
99	# the stack. Actually, I'd do it from within XS, but	176	=over 4
100	# I couldn't get it to work.	177
		178	=item async { ... } [@args...]
		179
		180	Create a new coroutine and return its coroutine object (usually
		181	unused). The coroutine will be put into the ready queue, so
		182	it will start running automatically on the next scheduler run.
		183
		184	The first argument is a codeblock/closure that should be executed in the
		185	coroutine. When it returns argument returns the coroutine is automatically
		186	terminated.
		187
		188	The remaining arguments are passed as arguments to the closure.
		189
		190	See the C<Coro::State::new> constructor for info about the coroutine
		191	environment in which coroutines are executed.
		192
		193	Calling C<exit> in a coroutine will do the same as calling exit outside
		194	the coroutine. Likewise, when the coroutine dies, the program will exit,
		195	just as it would in the main program.
		196
		197	If you do not want that, you can provide a default C<die> handler, or
		198	simply avoid dieing (by use of C<eval>).
		199
		200	Example: Create a new coroutine that just prints its arguments.
		201
		202	async {
		203	print "@_\n";
		204	} 1,2,3,4;
		205
		206	=cut
		207
		208	sub async(&@) {
		209	my $coro = new Coro @_;
		210	$coro->ready;
		211	$coro
		212	}
		213
		214	=item async_pool { ... } [@args...]
		215
		216	Similar to C<async>, but uses a coroutine pool, so you should not call
		217	terminate or join on it (although you are allowed to), and you get a
		218	coroutine that might have executed other code already (which can be good
		219	or bad :).
		220
		221	On the plus side, this function is about twice as fast as creating (and
		222	destroying) a completely new coroutine, so if you need a lot of generic
		223	coroutines in quick successsion, use C<async_pool>, not C<async>.
		224
		225	The code block is executed in an C<eval> context and a warning will be
		226	issued in case of an exception instead of terminating the program, as
		227	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>
		228	will not work in the expected way, unless you call terminate or cancel,
		229	which somehow defeats the purpose of pooling (but is fine in the
		230	exceptional case).
		231
		232	The priority will be reset to C<0> after each run, tracing will be
		233	disabled, the description will be reset and the default output filehandle
		234	gets restored, so you can change all these. Otherwise the coroutine will
		235	be re-used "as-is": most notably if you change other per-coroutine global
		236	stuff such as C<$/> you I<must needs> revert that change, which is most
		237	simply done by using local as in: C<< local $/ >>.
		238
		239	The idle pool size is limited to C<8> idle coroutines (this can be
		240	adjusted by changing $Coro::POOL_SIZE), but there can be as many non-idle
		241	coros as required.
		242
		243	If you are concerned about pooled coroutines growing a lot because a
		244	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
		245	{ terminate }> once per second or so to slowly replenish the pool. In
		246	addition to that, when the stacks used by a handler grows larger than 32kb
		247	(adjustable via $Coro::POOL_RSS) it will also be destroyed.
		248
		249	=cut
		250
		251	our $POOL_SIZE = 8;
		252	our $POOL_RSS = 32 * 1024;
		253	our @async_pool;
		254
		255	sub pool_handler {
		256	while () {
		257	eval {
		258	&{&_pool_handler} while 1;
		259	};
		260
		261	warn $@ if $@;
		262	}
		263	}
		264
		265	=back
		266
		267	=head1 STATIC METHODS
		268
		269	Static methods are actually functions that implicitly operate on the
		270	current coroutine.
		271
		272	=over 4
		273
		274	=item schedule
		275
		276	Calls the scheduler. The scheduler will find the next coroutine that is
		277	to be run from the ready queue and switches to it. The next coroutine
		278	to be run is simply the one with the highest priority that is longest
		279	in its ready queue. If there is no coroutine ready, it will clal the
		280	C<$Coro::idle> hook.
		281
		282	Please note that the current coroutine will I<not> be put into the ready
		283	queue, so calling this function usually means you will never be called
		284	again unless something else (e.g. an event handler) calls C<< ->ready >>,
		285	thus waking you up.
		286
		287	This makes C<schedule> I<the> generic method to use to block the current
		288	coroutine and wait for events: first you remember the current coroutine in
		289	a variable, then arrange for some callback of yours to call C<< ->ready
		290	>> on that once some event happens, and last you call C<schedule> to put
		291	yourself to sleep. Note that a lot of things can wake your coroutine up,
		292	so you need to check whether the event indeed happened, e.g. by storing the
		293	status in a variable.
		294
		295	See B<HOW TO WAIT FOR A CALLBACK>, below, for some ways to wait for callbacks.
		296
		297	=item cede
		298
		299	"Cede" to other coroutines. This function puts the current coroutine into
		300	the ready queue and calls C<schedule>, which has the effect of giving
		301	up the current "timeslice" to other coroutines of the same or higher
		302	priority. Once your coroutine gets its turn again it will automatically be
		303	resumed.
		304
		305	This function is often called C<yield> in other languages.
		306
		307	=item Coro::cede_notself
		308
		309	Works like cede, but is not exported by default and will cede to I<any>
		310	coroutine, regardless of priority. This is useful sometimes to ensure
		311	progress is made.
		312
		313	=item terminate [arg...]
		314
		315	Terminates the current coroutine with the given status values (see L<cancel>).
		316
		317	=item killall
		318
		319	Kills/terminates/cancels all coroutines except the currently running
		320	one. This can be useful after a fork, either in the child or the parent,
		321	as usually only one of them should inherit the running coroutines.
		322
		323	Note that in the implementation, destructors run as normal, making this
		324	function not so useful after a fork. Future versions of this function
		325	might try to free resources without running any code.
		326
		327	Note that while this will try to free some of the main programs resources,
		328	you cannot free all of them, so if a coroutine that is not the main
		329	program calls this function, there will be some one-time resource leak.
		330
		331	=cut
		332
		333	sub killall {
		334	for (Coro::State::list) {
		335	$_->cancel
		336	if $_ != $current && UNIVERSAL::isa $_, "Coro";
		337	}
		338	}
		339
		340	=back
		341
		342	=head1 COROUTINE OBJECT METHODS
		343
		344	These are the methods you can call on coroutine objects (or to create
		345	them).
		346
		347	=over 4
		348
		349	=item new Coro \&sub [, @args...]
		350
		351	Create a new coroutine and return it. When the sub returns, the coroutine
		352	automatically terminates as if C<terminate> with the returned values were
		353	called. To make the coroutine run you must first put it into the ready
		354	queue by calling the ready method.
		355
		356	See C<async> and C<Coro::State::new> for additional info about the
		357	coroutine environment.
		358
		359	=cut
		360
		361	sub _coro_run {
		362	terminate &{+shift};
		363	}
		364
		365	=item $success = $coroutine->ready
		366
		367	Put the given coroutine into the end of its ready queue (there is one
		368	queue for each priority) and return true. If the coroutine is already in
		369	the ready queue, do nothing and return false.
		370
		371	This ensures that the scheduler will resume this coroutine automatically
		372	once all the coroutines of higher priority and all coroutines of the same
		373	priority that were put into the ready queue earlier have been resumed.
		374
		375	=item $is_ready = $coroutine->is_ready
		376
		377	Return whether the coroutine is currently the ready queue or not,
		378
		379	=item $coroutine->cancel (arg...)
		380
		381	Terminates the given coroutine and makes it return the given arguments as
		382	status (default: the empty list). Never returns if the coroutine is the
		383	current coroutine.
		384
		385	=cut
		386
		387	sub cancel {
		388	my $self = shift;
		389
		390	if ($current == $self) {
		391	terminate @_;
		392	} else {
		393	$self->{_status} = [@_];
		394	$self->_cancel;
		395	}
		396	}
		397
		398	=item $coroutine->schedule_to
		399
		400	Puts the current coroutine to sleep (like C<Coro::schedule>), but instead
		401	of continuing with the next coro from the ready queue, always switch to
		402	the given coroutine object (regardless of priority etc.). The readyness
		403	state of that coroutine isn't changed.
		404
		405	This is an advanced method for special cases - I'd love to hear about any
		406	uses for this one.
		407
		408	=item $coroutine->cede_to
		409
		410	Like C<schedule_to>, but puts the current coroutine into the ready
		411	queue. This has the effect of temporarily switching to the given
		412	coroutine, and continuing some time later.
		413
		414	This is an advanced method for special cases - I'd love to hear about any
		415	uses for this one.
		416
		417	=item $coroutine->throw ([$scalar])
		418
		419	If C<$throw> is specified and defined, it will be thrown as an exception
		420	inside the coroutine at the next convenient point in time. Otherwise
		421	clears the exception object.
		422
		423	Coro will check for the exception each time a schedule-like-function
		424	returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down
		425	>>, C<< Coro::Handle->readable >> and so on. Most of these functions
		426	detect this case and return early in case an exception is pending.
		427
		428	The exception object will be thrown "as is" with the specified scalar in
		429	C<$@>, i.e. if it is a string, no line number or newline will be appended
		430	(unlike with C<die>).
		431
		432	This can be used as a softer means than C<cancel> to ask a coroutine to
		433	end itself, although there is no guarantee that the exception will lead to
		434	termination, and if the exception isn't caught it might well end the whole
		435	program.
		436
		437	You might also think of C<throw> as being the moral equivalent of
		438	C<kill>ing a coroutine with a signal (in this case, a scalar).
		439
		440	=item $coroutine->join
		441
		442	Wait until the coroutine terminates and return any values given to the
		443	C<terminate> or C<cancel> functions. C<join> can be called concurrently
		444	from multiple coroutines, and all will be resumed and given the status
		445	return once the C<$coroutine> terminates.
		446
		447	=cut
		448
		449	sub join {
		450	my $self = shift;
		451
		452	unless ($self->{_status}) {
		453	my $current = $current;
		454
		455	push @{$self->{_on_destroy}}, sub {
		456	$current->ready;
		457	undef $current;
		458	};
		459
		460	&schedule while $current;
		461	}
		462
		463	wantarray ? @{$self->{_status}} : $self->{_status}[0];
		464	}
		465
		466	=item $coroutine->on_destroy (\&cb)
		467
		468	Registers a callback that is called when this coroutine gets destroyed,
		469	but before it is joined. The callback gets passed the terminate arguments,
		470	if any, and I<must not> die, under any circumstances.
		471
		472	=cut
		473
		474	sub on_destroy {
		475	my ($self, $cb) = @_;
		476
		477	push @{ $self->{_on_destroy} }, $cb;
		478	}
		479
		480	=item $oldprio = $coroutine->prio ($newprio)
		481
		482	Sets (or gets, if the argument is missing) the priority of the
		483	coroutine. Higher priority coroutines get run before lower priority
		484	coroutines. Priorities are small signed integers (currently -4 .. +3),
		485	that you can refer to using PRIO_xxx constants (use the import tag :prio
		486	to get then):
		487
		488	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
		489	3 > 1 > 0 > -1 > -3 > -4
		490
		491	# set priority to HIGH
		492	current->prio(PRIO_HIGH);
		493
		494	The idle coroutine ($Coro::idle) always has a lower priority than any
		495	existing coroutine.
		496
		497	Changing the priority of the current coroutine will take effect immediately,
		498	but changing the priority of coroutines in the ready queue (but not
		499	running) will only take effect after the next schedule (of that
		500	coroutine). This is a bug that will be fixed in some future version.
		501
		502	=item $newprio = $coroutine->nice ($change)
		503
		504	Similar to C<prio>, but subtract the given value from the priority (i.e.
		505	higher values mean lower priority, just as in unix).
		506
		507	=item $olddesc = $coroutine->desc ($newdesc)
		508
		509	Sets (or gets in case the argument is missing) the description for this
		510	coroutine. This is just a free-form string you can associate with a
		511	coroutine.
		512
		513	This method simply sets the C<< $coroutine->{desc} >> member to the given
		514	string. You can modify this member directly if you wish.
		515
		516	=cut
		517
		518	sub desc {
		519	my $old = $_[0]{desc};
		520	$_[0]{desc} = $_[1] if @_ > 1;
		521	$old;
		522	}
		523
101	sub transfer {	524	sub transfer {
102	_transfer($_[0], $_[1]);	525	require Carp;
		526	Carp::croak ("You must not call ->transfer on Coro objects. Use Coro::State objects or the ->schedule_to method. Caught");
103	}	527	}
104		528
105	=item $error, $error_msg, $error_coro	529	=back
106		530
107	This coroutine will be called on fatal errors. C<$error_msg> and	531	=head1 GLOBAL FUNCTIONS
108	C<$error_coro> return the error message and the error-causing coroutine
109	(NOT an object) respectively. This API might change.
110		532
111	=cut	533	=over 4
112		534
113	$error_msg =	535	=item Coro::nready
114	$error_coro = undef;
115		536
116	$error = _newprocess {	537	Returns the number of coroutines that are currently in the ready state,
117	print STDERR "FATAL: $error_msg\nprogram aborted\n";	538	i.e. that can be switched to by calling C<schedule> directory or
118	exit 50;	539	indirectly. The value C<0> means that the only runnable coroutine is the
		540	currently running one, so C<cede> would have no effect, and C<schedule>
		541	would cause a deadlock unless there is an idle handler that wakes up some
		542	coroutines.
		543
		544	=item my $guard = Coro::guard { ... }
		545
		546	This function still exists, but is deprecated. Please use the
		547	C<Guard::guard> function instead.
		548
		549	=cut
		550
		551	BEGIN { *guard = \&Guard::guard }
		552
		553	=item unblock_sub { ... }
		554
		555	This utility function takes a BLOCK or code reference and "unblocks" it,
		556	returning a new coderef. Unblocking means that calling the new coderef
		557	will return immediately without blocking, returning nothing, while the
		558	original code ref will be called (with parameters) from within another
		559	coroutine.
		560
		561	The reason this function exists is that many event libraries (such as the
		562	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form
		563	of reentrancy). This means you must not block within event callbacks,
		564	otherwise you might suffer from crashes or worse. The only event library
		565	currently known that is safe to use without C<unblock_sub> is L<EV>.
		566
		567	This function allows your callbacks to block by executing them in another
		568	coroutine where it is safe to block. One example where blocking is handy
		569	is when you use the L<Coro::AIO\|Coro::AIO> functions to save results to
		570	disk, for example.
		571
		572	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when
		573	creating event callbacks that want to block.
		574
		575	If your handler does not plan to block (e.g. simply sends a message to
		576	another coroutine, or puts some other coroutine into the ready queue),
		577	there is no reason to use C<unblock_sub>.
		578
		579	Note that you also need to use C<unblock_sub> for any other callbacks that
		580	are indirectly executed by any C-based event loop. For example, when you
		581	use a module that uses L<AnyEvent> (and you use L<Coro::AnyEvent>) and it
		582	provides callbacks that are the result of some event callback, then you
		583	must not block either, or use C<unblock_sub>.
		584
		585	=cut
		586
		587	our @unblock_queue;
		588
		589	# we create a special coro because we want to cede,
		590	# to reduce pressure on the coro pool (because most callbacks
		591	# return immediately and can be reused) and because we cannot cede
		592	# inside an event callback.
		593	our $unblock_scheduler = new Coro sub {
		594	while () {
		595	while (my $cb = pop @unblock_queue) {
		596	&async_pool (@$cb);
		597
		598	# for short-lived callbacks, this reduces pressure on the coro pool
		599	# as the chance is very high that the async_poll coro will be back
		600	# in the idle state when cede returns
		601	cede;
		602	}
		603	schedule; # sleep well
		604	}
119	};	605	};
		606	$unblock_scheduler->{desc} = "[unblock_sub scheduler]";
		607
		608	sub unblock_sub(&) {
		609	my $cb = shift;
		610
		611	sub {
		612	unshift @unblock_queue, [$cb, @_];
		613	$unblock_scheduler->ready;
		614	}
		615	}
		616
		617	=item $cb = Coro::rouse_cb
		618
		619	Create and return a "rouse callback". That's a code reference that,
		620	when called, will remember a copy of its arguments and notify the owner
		621	coroutine of the callback.
		622
		623	See the next function.
		624
		625	=item @args = Coro::rouse_wait [$cb]
		626
		627	Wait for the specified rouse callback (or the last one that was created in
		628	this coroutine).
		629
		630	As soon as the callback is invoked (or when the callback was invoked
		631	before C<rouse_wait>), it will return the arguments originally passed to
		632	the rouse callback.
		633
		634	See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example.
		635
		636	=back
		637
		638	=cut
120		639
121	1;	640	1;
122		641
		642	=head1 HOW TO WAIT FOR A CALLBACK
		643
		644	It is very common for a coroutine to wait for some callback to be
		645	called. This occurs naturally when you use coroutines in an otherwise
		646	event-based program, or when you use event-based libraries.
		647
		648	These typically register a callback for some event, and call that callback
		649	when the event occured. In a coroutine, however, you typically want to
		650	just wait for the event, simplyifying things.
		651
		652	For example C<< AnyEvent->child >> registers a callback to be called when
		653	a specific child has exited:
		654
		655	my $child_watcher = AnyEvent->child (pid => $pid, cb => sub { ... });
		656
		657	But from withina coroutine, you often just want to write this:
		658
		659	my $status = wait_for_child $pid;
		660
		661	Coro offers two functions specifically designed to make this easy,
		662	C<Coro::rouse_cb> and C<Coro::rouse_wait>.
		663
		664	The first function, C<rouse_cb>, generates and returns a callback that,
		665	when invoked, will save its arguments and notify the coroutine that
		666	created the callback.
		667
		668	The second function, C<rouse_wait>, waits for the callback to be called
		669	(by calling C<schedule> to go to sleep) and returns the arguments
		670	originally passed to the callback.
		671
		672	Using these functions, it becomes easy to write the C<wait_for_child>
		673	function mentioned above:
		674
		675	sub wait_for_child($) {
		676	my ($pid) = @_;
		677
		678	my $watcher = AnyEvent->child (pid => $pid, cb => Coro::rouse_cb);
		679
		680	my ($rpid, $rstatus) = Coro::rouse_wait;
		681	$rstatus
		682	}
		683
		684	In the case where C<rouse_cb> and C<rouse_wait> are not flexible enough,
		685	you can roll your own, using C<schedule>:
		686
		687	sub wait_for_child($) {
		688	my ($pid) = @_;
		689
		690	# store the current coroutine in $current,
		691	# and provide result variables for the closure passed to ->child
		692	my $current = $Coro::current;
		693	my ($done, $rstatus);
		694
		695	# pass a closure to ->child
		696	my $watcher = AnyEvent->child (pid => $pid, cb => sub {
		697	$rstatus = $_[1]; # remember rstatus
		698	$done = 1; # mark $rstatus as valud
		699	});
		700
		701	# wait until the closure has been called
		702	schedule while !$done;
		703
		704	$rstatus
		705	}
		706
		707
		708	=head1 BUGS/LIMITATIONS
		709
		710	=over 4
		711
		712	=item fork with pthread backend
		713
		714	When Coro is compiled using the pthread backend (which isn't recommended
		715	but required on many BSDs as their libcs are completely broken), then
		716	coroutines will not survive a fork. There is no known workaround except to
		717	fix your libc and use a saner backend.
		718
		719	=item perl process emulation ("threads")
		720
		721	This module is not perl-pseudo-thread-safe. You should only ever use this
		722	module from the first thread (this requirement might be removed in the
		723	future to allow per-thread schedulers, but Coro::State does not yet allow
		724	this). I recommend disabling thread support and using processes, as having
		725	the windows process emulation enabled under unix roughly halves perl
		726	performance, even when not used.
		727
		728	=item coroutine switching not signal safe
		729
		730	You must not switch to another coroutine from within a signal handler
		731	(only relevant with %SIG - most event libraries provide safe signals).
		732
		733	That means you I<MUST NOT> call any function that might "block" the
		734	current coroutine - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or
		735	anything that calls those. Everything else, including calling C<ready>,
		736	works.
		737
123	=back	738	=back
124		739
125	=head1 BUGS
126
127	This module has not yet been extensively tested.
128		740
129	=head1 SEE ALSO	741	=head1 SEE ALSO
130		742
131	L<Coro::Process>, L<Coro::Signal>.	743	Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>.
		744
		745	Debugging: L<Coro::Debug>.
		746
		747	Support/Utility: L<Coro::Specific>, L<Coro::Util>.
		748
		749	Locking and IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>,
		750	L<Coro::SemaphoreSet>, L<Coro::RWLock>.
		751
		752	I/O and Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>.
		753
		754	Compatibility with other modules: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for
		755	a better-working alternative), L<Coro::BDB>, L<Coro::Storable>,
		756	L<Coro::Select>.
		757
		758	XS API: L<Coro::MakeMaker>.
		759
		760	Low level Configuration, Thread Environment, Continuations: L<Coro::State>.
132		761
133	=head1 AUTHOR	762	=head1 AUTHOR
134		763
135	Marc Lehmann <pcg@goof.com>	764	Marc Lehmann <schmorp@schmorp.de>
136	http://www.goof.com/pcg/marc/	765	http://home.schmorp.de/
137		766
138	=cut	767	=cut
139		768

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.7 by root, Fri Jul 13 13:05:38 2001 UTC vs. Revision 1.245 by root, Sun Dec 14 19:52:58 2008 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.7 by root, Fri Jul 13 13:05:38 2001 UTC vs.
Revision 1.245 by root, Sun Dec 14 19:52:58 2008 UTC