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

Comparing Coro/Coro.pm (file contents):
Revision 1.66 by root, Thu Mar 3 17:20:31 2005 UTC vs.
Revision 1.232 by root, Fri Nov 21 02:39:40 2008 UTC

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

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.66 by root, Thu Mar 3 17:20:31 2005 UTC vs. Revision 1.232 by root, Fri Nov 21 02:39:40 2008 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.66 by root, Thu Mar 3 17:20:31 2005 UTC vs.
Revision 1.232 by root, Fri Nov 21 02:39:40 2008 UTC