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

Comparing Coro/Coro.pm (file contents):
Revision 1.91 by root, Fri Dec 1 02:17:37 2006 UTC vs.
Revision 1.152 by root, Sun Oct 7 13:53:37 2007 UTC

…		…
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	};
		15	print "1\n";
		16	cede; # yield to coroutine
		17	print "3\n";
		18	cede; # and again
12		19
13	# alternatively create an async process like this:	20	# use locking
		21	my $lock = new Coro::Semaphore;
		22	my $locked;
14		23
15	sub some_func : Coro {	24	$lock->down;
16	# some more async code	25	$locked = 1;
17	}	26	$lock->up;
18
19	cede;
20		27
21	=head1 DESCRIPTION	28	=head1 DESCRIPTION
22		29
23	This module collection manages coroutines. Coroutines are similar to	30	This module collection manages coroutines. Coroutines are similar
24	threads but don't run in parallel.	31	to threads but don't run in parallel at the same time even on SMP
		32	machines. The specific flavor of coroutine used in this module also
		33	guarantees you that it will not switch between coroutines unless
		34	necessary, at easily-identified points in your program, so locking and
		35	parallel access are rarely an issue, making coroutine programming much
		36	safer than threads programming.
25		37
		38	(Perl, however, does not natively support real threads but instead does a
		39	very slow and memory-intensive emulation of processes using threads. This
		40	is a performance win on Windows machines, and a loss everywhere else).
		41
26	In this module, coroutines are defined as "callchain + lexical variables	42	In this module, coroutines are defined as "callchain + lexical variables +
27	+ @_ + $_ + $@ + $^W + C stack), that is, a coroutine has it's own	43	@_ + $_ + $@ + $/ + 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	44	its own set of lexicals and its own set of perls most important global
29	important global variables.	45	variables (see L<Coro::State> for more configuration).
30		46
31	=cut	47	=cut
32		48
33	package Coro;	49	package Coro;
34		50
…		…
41		57
42	our $idle; # idle handler	58	our $idle; # idle handler
43	our $main; # main coroutine	59	our $main; # main coroutine
44	our $current; # current coroutine	60	our $current; # current coroutine
45		61
46	our $VERSION = '3.0';	62	our $VERSION = '4.1';
47		63
48	our @EXPORT = qw(async cede schedule terminate current);	64	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
49	our %EXPORT_TAGS = (	65	our %EXPORT_TAGS = (
50	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],	66	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
51	);	67	);
52	our @EXPORT_OK = @{$EXPORT_TAGS{prio}};	68	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));
53		69
54	{	70	{
55	my @async;	71	my @async;
56	my $init;	72	my $init;
57		73
58	# this way of handling attributes simply is NOT scalable ;()	74	# this way of handling attributes simply is NOT scalable ;()
59	sub import {	75	sub import {
60	no strict 'refs';	76	no strict 'refs';
61		77
62	Coro->export_to_level(1, @_);	78	Coro->export_to_level (1, @_);
63		79
64	my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};	80	my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
65	*{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {	81	*{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {
66	my ($package, $ref) = (shift, shift);	82	my ($package, $ref) = (shift, shift);
67	my @attrs;	83	my @attrs;
…		…
99		115
100	The current coroutine (the last coroutine switched to). The initial value	116	The current coroutine (the last coroutine switched to). The initial value
101	is C<$main> (of course).	117	is C<$main> (of course).
102		118
103	This variable is B<strictly> I<read-only>. It is provided for performance	119	This variable is B<strictly> I<read-only>. It is provided for performance
104	reasons. If performance is not essentiel you are encouraged to use the	120	reasons. If performance is not essential you are encouraged to use the
105	C<Coro::current> function instead.	121	C<Coro::current> function instead.
106		122
107	=cut	123	=cut
108		124
		125	$main->{desc} = "[main::]";
		126
109	# maybe some other module used Coro::Specific before...	127	# maybe some other module used Coro::Specific before...
110	if ($current) {
111	$main->{specific} = $current->{specific};	128	$main->{_specific} = $current->{_specific}
112	}	129	if $current;
113		130
114	$current = $main;	131	_set_current $main;
115		132
116	sub current() { $current }	133	sub current() { $current }
117		134
118	=item $idle	135	=item $idle
119		136
…		…
124	This hook is overwritten by modules such as C<Coro::Timer> and	141	This hook is overwritten by modules such as C<Coro::Timer> and
125	C<Coro::Event> to wait on an external event that hopefully wake up a	142	C<Coro::Event> to wait on an external event that hopefully wake up a
126	coroutine so the scheduler can run it.	143	coroutine so the scheduler can run it.
127		144
128	Please note that if your callback recursively invokes perl (e.g. for event	145	Please note that if your callback recursively invokes perl (e.g. for event
129	handlers), then it must be prepared to be called recursively.	146	handlers), then it must be prepared to be called recursively itself.
130		147
131	=cut	148	=cut
132		149
133	$idle = sub {	150	$idle = sub {
134	print STDERR "FATAL: deadlock detected\n";	151	require Carp;
135	exit (51);	152	Carp::croak ("FATAL: deadlock detected");
136	};	153	};
		154
		155	sub _cancel {
		156	my ($self) = @_;
		157
		158	# free coroutine data and mark as destructed
		159	$self->_destroy
		160	or return;
		161
		162	# call all destruction callbacks
		163	$_->(@{$self->{_status}})
		164	for @{(delete $self->{_on_destroy}) \|\| []};
		165	}
137		166
138	# this coroutine is necessary because a coroutine	167	# this coroutine is necessary because a coroutine
139	# cannot destroy itself.	168	# cannot destroy itself.
140	my @destroy;	169	my @destroy;
		170	my $manager;
		171
141	my $manager; $manager = new Coro sub {	172	$manager = new Coro sub {
142	while () {	173	while () {
143	# by overwriting the state object with the manager we destroy it	174	(shift @destroy)->_cancel
144	# while still being able to schedule this coroutine (in case it has
145	# been readied multiple times. this is harmless since the manager
146	# can be called as many times as neccessary and will always
147	# remove itself from the runqueue
148	while (@destroy) {	175	while @destroy;
149	my $coro = pop @destroy;
150	$coro->{status} \|\|= [];
151	$_->ready for @{delete $coro->{join} \|\| []};
152		176
153	# the next line destroys the coro state, but keeps the
154	# process itself intact (we basically make it a zombie
155	# process that always runs the manager thread, so it's possible
156	# to transfer() to this process).
157	$coro->_clone_state_from ($manager);
158	}
159	&schedule;	177	&schedule;
160	}	178	}
161	};	179	};
		180	$manager->desc ("[coro manager]");
		181	$manager->prio (PRIO_MAX);
162		182
163	# static methods. not really.	183	# static methods. not really.
164		184
165	=back	185	=back
166		186
167	=head2 STATIC METHODS	187	=head2 STATIC METHODS
168		188
169	Static methods are actually functions that operate on the current process only.	189	Static methods are actually functions that operate on the current coroutine only.
170		190
171	=over 4	191	=over 4
172		192
173	=item async { ... } [@args...]	193	=item async { ... } [@args...]
174		194
175	Create a new asynchronous process and return it's process object	195	Create a new asynchronous coroutine and return it's coroutine object
176	(usually unused). When the sub returns the new process is automatically	196	(usually unused). When the sub returns the new coroutine is automatically
177	terminated.	197	terminated.
178		198
179	Calling C<exit> in a coroutine will not work correctly, so do not do that.	199	See the C<Coro::State::new> constructor for info about the coroutine
		200	environment in which coroutines run.
180		201
181	When the coroutine dies, the program will exit, just as in the main	202	Calling C<exit> in a coroutine will do the same as calling exit outside
182	program.	203	the coroutine. Likewise, when the coroutine dies, the program will exit,
		204	just as it would in the main program.
183		205
184	# create a new coroutine that just prints its arguments	206	# create a new coroutine that just prints its arguments
185	async {	207	async {
186	print "@_\n";	208	print "@_\n";
187	} 1,2,3,4;	209	} 1,2,3,4;
188		210
189	=cut	211	=cut
190		212
191	sub async(&@) {	213	sub async(&@) {
192	my $pid = new Coro @_;	214	my $coro = new Coro @_;
193	$pid->ready;	215	$coro->ready;
194	$pid	216	$coro
		217	}
		218
		219	=item async_pool { ... } [@args...]
		220
		221	Similar to C<async>, but uses a coroutine pool, so you should not call
		222	terminate or join (although you are allowed to), and you get a coroutine
		223	that might have executed other code already (which can be good or bad :).
		224
		225	Also, the 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.
		230
		231	The priority will be reset to C<0> after each job, tracing will be
		232	disabled, the description will be reset and the default output filehandle
		233	gets restored, so you can change alkl these. Otherwise the coroutine will
		234	be re-used "as-is": most notably if you change other per-coroutine global
		235	stuff such as C<$/> you need to revert that change, which is most simply
		236	done by using local as in C< local $/ >.
		237
		238	The pool size is limited to 8 idle coroutines (this can be adjusted by
		239	changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
		240	required.
		241
		242	If you are concerned about pooled coroutines growing a lot because a
		243	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
		244	{ terminate }> once per second or so to slowly replenish the pool. In
		245	addition to that, when the stacks used by a handler grows larger than 16kb
		246	(adjustable with $Coro::POOL_RSS) it will also exit.
		247
		248	=cut
		249
		250	our $POOL_SIZE = 8;
		251	our $POOL_RSS = 16 * 1024;
		252	our @async_pool;
		253
		254	sub pool_handler {
		255	my $cb;
		256
		257	while () {
		258	eval {
		259	while () {
		260	_pool_1 $cb;
		261	&$cb;
		262	_pool_2 $cb;
		263	&schedule;
		264	}
		265	};
		266
		267	last if $@ eq "\3async_pool terminate\2\n";
		268	warn $@ if $@;
		269	}
		270	}
		271
		272	sub async_pool(&@) {
		273	# this is also inlined into the unlock_scheduler
		274	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
		275
		276	$coro->{_invoke} = [@_];
		277	$coro->ready;
		278
		279	$coro
195	}	280	}
196		281
197	=item schedule	282	=item schedule
198		283
199	Calls the scheduler. Please note that the current process will not be put	284	Calls the scheduler. Please note that the current coroutine will not be put
200	into the ready queue, so calling this function usually means you will	285	into the ready queue, so calling this function usually means you will
201	never be called again unless something else (e.g. an event handler) calls	286	never be called again unless something else (e.g. an event handler) calls
202	ready.	287	ready.
203		288
204	The canonical way to wait on external events is this:	289	The canonical way to wait on external events is this:
205		290
206	{	291	{
207	# remember current process	292	# remember current coroutine
208	my $current = $Coro::current;	293	my $current = $Coro::current;
209		294
210	# register a hypothetical event handler	295	# register a hypothetical event handler
211	on_event_invoke sub {	296	on_event_invoke sub {
212	# wake up sleeping coroutine	297	# wake up sleeping coroutine
213	$current->ready;	298	$current->ready;
214	undef $current;	299	undef $current;
215	};	300	};
216		301
217	# call schedule until event occured.	302	# call schedule until event occurred.
218	# in case we are woken up for other reasons	303	# in case we are woken up for other reasons
219	# (current still defined), loop.	304	# (current still defined), loop.
220	Coro::schedule while $current;	305	Coro::schedule while $current;
221	}	306	}
222		307
223	=cut
224
225	=item cede	308	=item cede
226		309
227	"Cede" to other processes. This function puts the current process into the	310	"Cede" to other coroutines. This function puts the current coroutine into the
228	ready queue and calls C<schedule>, which has the effect of giving up the	311	ready queue and calls C<schedule>, which has the effect of giving up the
229	current "timeslice" to other coroutines of the same or higher priority.	312	current "timeslice" to other coroutines of the same or higher priority.
230		313
231	=cut	314	Returns true if at least one coroutine switch has happened.
		315
		316	=item Coro::cede_notself
		317
		318	Works like cede, but is not exported by default and will cede to any
		319	coroutine, regardless of priority, once.
		320
		321	Returns true if at least one coroutine switch has happened.
232		322
233	=item terminate [arg...]	323	=item terminate [arg...]
234		324
235	Terminates the current process with the given status values (see L<cancel>).	325	Terminates the current coroutine with the given status values (see L<cancel>).
		326
		327	=item killall
		328
		329	Kills/terminates/cancels all coroutines except the currently running
		330	one. This is useful after a fork, either in the child or the parent, as
		331	usually only one of them should inherit the running coroutines.
236		332
237	=cut	333	=cut
238		334
239	sub terminate {	335	sub terminate {
240	$current->cancel (@_);	336	$current->cancel (@_);
241	}	337	}
242		338
		339	sub killall {
		340	for (Coro::State::list) {
		341	$_->cancel
		342	if $_ != $current && UNIVERSAL::isa $_, "Coro";
		343	}
		344	}
		345
243	=back	346	=back
244		347
245	# dynamic methods	348	# dynamic methods
246		349
247	=head2 PROCESS METHODS	350	=head2 COROUTINE METHODS
248		351
249	These are the methods you can call on process objects.	352	These are the methods you can call on coroutine objects.
250		353
251	=over 4	354	=over 4
252		355
253	=item new Coro \&sub [, @args...]	356	=item new Coro \&sub [, @args...]
254		357
255	Create a new process and return it. When the sub returns the process	358	Create a new coroutine and return it. When the sub returns the coroutine
256	automatically terminates as if C<terminate> with the returned values were	359	automatically terminates as if C<terminate> with the returned values were
257	called. To make the process run you must first put it into the ready queue	360	called. To make the coroutine run you must first put it into the ready queue
258	by calling the ready method.	361	by calling the ready method.
259		362
260	Calling C<exit> in a coroutine will not work correctly, so do not do that.	363	See C<async> and C<Coro::State::new> for additional info about the
		364	coroutine environment.
261		365
262	=cut	366	=cut
263		367
264	sub _new_coro {	368	sub _run_coro {
265	terminate &{+shift};	369	terminate &{+shift};
266	}	370	}
267		371
268	sub new {	372	sub new {
269	my $class = shift;	373	my $class = shift;
270		374
271	$class->SUPER::new (\&_new_coro, @_)	375	$class->SUPER::new (\&_run_coro, @_)
272	}	376	}
273		377
274	=item $success = $process->ready	378	=item $success = $coroutine->ready
275		379
276	Put the given process into the ready queue (according to it's priority)	380	Put the given coroutine into the ready queue (according to it's priority)
277	and return true. If the process is already in the ready queue, do nothing	381	and return true. If the coroutine is already in the ready queue, do nothing
278	and return false.	382	and return false.
279		383
280	=item $is_ready = $process->is_ready	384	=item $is_ready = $coroutine->is_ready
281		385
282	Return wether the process is currently the ready queue or not,	386	Return wether the coroutine is currently the ready queue or not,
283		387
284	=item $process->cancel (arg...)	388	=item $coroutine->cancel (arg...)
285		389
286	Terminates the given process and makes it return the given arguments as	390	Terminates the given coroutine and makes it return the given arguments as
287	status (default: the empty list).	391	status (default: the empty list). Never returns if the coroutine is the
		392	current coroutine.
288		393
289	=cut	394	=cut
290		395
291	sub cancel {	396	sub cancel {
292	my $self = shift;	397	my $self = shift;
293	$self->{status} = [@_];	398	$self->{_status} = [@_];
		399
		400	if ($current == $self) {
294	push @destroy, $self;	401	push @destroy, $self;
295	$manager->ready;	402	$manager->ready;
296	&schedule if $current == $self;	403	&schedule while 1;
		404	} else {
		405	$self->_cancel;
		406	}
297	}	407	}
298		408
299	=item $process->join	409	=item $coroutine->join
300		410
301	Wait until the coroutine terminates and return any values given to the	411	Wait until the coroutine terminates and return any values given to the
302	C<terminate> or C<cancel> functions. C<join> can be called multiple times	412	C<terminate> or C<cancel> functions. C<join> can be called concurrently
303	from multiple processes.	413	from multiple coroutines.
304		414
305	=cut	415	=cut
306		416
307	sub join {	417	sub join {
308	my $self = shift;	418	my $self = shift;
		419
309	unless ($self->{status}) {	420	unless ($self->{_status}) {
310	push @{$self->{join}}, $current;	421	my $current = $current;
311	&schedule;	422
		423	push @{$self->{_on_destroy}}, sub {
		424	$current->ready;
		425	undef $current;
		426	};
		427
		428	&schedule while $current;
312	}	429	}
		430
313	wantarray ? @{$self->{status}} : $self->{status}[0];	431	wantarray ? @{$self->{_status}} : $self->{_status}[0];
314	}	432	}
315		433
		434	=item $coroutine->on_destroy (\&cb)
		435
		436	Registers a callback that is called when this coroutine gets destroyed,
		437	but before it is joined. The callback gets passed the terminate arguments,
		438	if any.
		439
		440	=cut
		441
		442	sub on_destroy {
		443	my ($self, $cb) = @_;
		444
		445	push @{ $self->{_on_destroy} }, $cb;
		446	}
		447
316	=item $oldprio = $process->prio ($newprio)	448	=item $oldprio = $coroutine->prio ($newprio)
317		449
318	Sets (or gets, if the argument is missing) the priority of the	450	Sets (or gets, if the argument is missing) the priority of the
319	process. Higher priority processes get run before lower priority	451	coroutine. Higher priority coroutines get run before lower priority
320	processes. Priorities are small signed integers (currently -4 .. +3),	452	coroutines. Priorities are small signed integers (currently -4 .. +3),
321	that you can refer to using PRIO_xxx constants (use the import tag :prio	453	that you can refer to using PRIO_xxx constants (use the import tag :prio
322	to get then):	454	to get then):
323		455
324	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN	456	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
325	3 > 1 > 0 > -1 > -3 > -4	457	3 > 1 > 0 > -1 > -3 > -4
…		…
328	current->prio(PRIO_HIGH);	460	current->prio(PRIO_HIGH);
329		461
330	The idle coroutine ($Coro::idle) always has a lower priority than any	462	The idle coroutine ($Coro::idle) always has a lower priority than any
331	existing coroutine.	463	existing coroutine.
332		464
333	Changing the priority of the current process will take effect immediately,	465	Changing the priority of the current coroutine will take effect immediately,
334	but changing the priority of processes in the ready queue (but not	466	but changing the priority of coroutines in the ready queue (but not
335	running) will only take effect after the next schedule (of that	467	running) will only take effect after the next schedule (of that
336	process). This is a bug that will be fixed in some future version.	468	coroutine). This is a bug that will be fixed in some future version.
337		469
338	=item $newprio = $process->nice ($change)	470	=item $newprio = $coroutine->nice ($change)
339		471
340	Similar to C<prio>, but subtract the given value from the priority (i.e.	472	Similar to C<prio>, but subtract the given value from the priority (i.e.
341	higher values mean lower priority, just as in unix).	473	higher values mean lower priority, just as in unix).
342		474
343	=item $olddesc = $process->desc ($newdesc)	475	=item $olddesc = $coroutine->desc ($newdesc)
344		476
345	Sets (or gets in case the argument is missing) the description for this	477	Sets (or gets in case the argument is missing) the description for this
346	process. This is just a free-form string you can associate with a process.	478	coroutine. This is just a free-form string you can associate with a coroutine.
		479
		480	This method simply sets the C<< $coroutine->{desc} >> member to the given string. You
		481	can modify this member directly if you wish.
		482
		483	=item $coroutine->throw ([$scalar])
		484
		485	If C<$throw> is specified and defined, it will be thrown as an exception
		486	inside the coroutine at the next convinient point in time (usually after
		487	it gains control at the next schedule/transfer/cede). Otherwise clears the
		488	exception object.
		489
		490	The exception object will be thrown "as is" with the specified scalar in
		491	C<$@>, i.e. if it is a string, no line number or newline will be appended
		492	(unlike with C<die>).
		493
		494	This can be used as a softer means than C<cancel> to ask a coroutine to
		495	end itself, although there is no guarentee that the exception will lead to
		496	termination, and if the exception isn't caught it might well end the whole
		497	program.
347		498
348	=cut	499	=cut
349		500
350	sub desc {	501	sub desc {
351	my $old = $_[0]{desc};	502	my $old = $_[0]{desc};
…		…
353	$old;	504	$old;
354	}	505	}
355		506
356	=back	507	=back
357		508
		509	=head2 GLOBAL FUNCTIONS
		510
		511	=over 4
		512
		513	=item Coro::nready
		514
		515	Returns the number of coroutines that are currently in the ready state,
		516	i.e. that can be switched to. The value C<0> means that the only runnable
		517	coroutine is the currently running one, so C<cede> would have no effect,
		518	and C<schedule> would cause a deadlock unless there is an idle handler
		519	that wakes up some coroutines.
		520
		521	=item my $guard = Coro::guard { ... }
		522
		523	This creates and returns a guard object. Nothing happens until the object
		524	gets destroyed, in which case the codeblock given as argument will be
		525	executed. This is useful to free locks or other resources in case of a
		526	runtime error or when the coroutine gets canceled, as in both cases the
		527	guard block will be executed. The guard object supports only one method,
		528	C<< ->cancel >>, which will keep the codeblock from being executed.
		529
		530	Example: set some flag and clear it again when the coroutine gets canceled
		531	or the function returns:
		532
		533	sub do_something {
		534	my $guard = Coro::guard { $busy = 0 };
		535	$busy = 1;
		536
		537	# do something that requires $busy to be true
		538	}
		539
		540	=cut
		541
		542	sub guard(&) {
		543	bless \(my $cb = $_[0]), "Coro::guard"
		544	}
		545
		546	sub Coro::guard::cancel {
		547	${$_[0]} = sub { };
		548	}
		549
		550	sub Coro::guard::DESTROY {
		551	${$_[0]}->();
		552	}
		553
		554
		555	=item unblock_sub { ... }
		556
		557	This utility function takes a BLOCK or code reference and "unblocks" it,
		558	returning the new coderef. This means that the new coderef will return
		559	immediately without blocking, returning nothing, while the original code
		560	ref will be called (with parameters) from within its own coroutine.
		561
		562	The reason this function exists is that many event libraries (such as the
		563	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form
		564	of thread-safety). This means you must not block within event callbacks,
		565	otherwise you might suffer from crashes or worse.
		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.
		571
		572	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when
		573	creating event callbacks that want to block.
		574
		575	=cut
		576
		577	our @unblock_queue;
		578
		579	# we create a special coro because we want to cede,
		580	# to reduce pressure on the coro pool (because most callbacks
		581	# return immediately and can be reused) and because we cannot cede
		582	# inside an event callback.
		583	our $unblock_scheduler = new Coro sub {
		584	while () {
		585	while (my $cb = pop @unblock_queue) {
		586	# this is an inlined copy of async_pool
		587	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
		588
		589	$coro->{_invoke} = $cb;
		590	$coro->ready;
		591	cede; # for short-lived callbacks, this reduces pressure on the coro pool
		592	}
		593	schedule; # sleep well
		594	}
		595	};
		596	$unblock_scheduler->desc ("[unblock_sub scheduler]");
		597
		598	sub unblock_sub(&) {
		599	my $cb = shift;
		600
		601	sub {
		602	unshift @unblock_queue, [$cb, @_];
		603	$unblock_scheduler->ready;
		604	}
		605	}
		606
		607	=back
		608
358	=cut	609	=cut
359		610
360	1;	611	1;
361		612
362	=head1 BUGS/LIMITATIONS	613	=head1 BUGS/LIMITATIONS
363		614
364	- you must make very sure that no coro is still active on global	615	- you must make very sure that no coro is still active on global
365	destruction. very bad things might happen otherwise (usually segfaults).	616	destruction. very bad things might happen otherwise (usually segfaults).
366		617
367	- this module is not thread-safe. You should only ever use this module	618	- this module is not thread-safe. You should only ever use this module
368	from the same thread (this requirement might be losened in the future	619	from the same thread (this requirement might be loosened in the future
369	to allow per-thread schedulers, but Coro::State does not yet allow	620	to allow per-thread schedulers, but Coro::State does not yet allow
370	this).	621	this).
371		622
372	=head1 SEE ALSO	623	=head1 SEE ALSO
373		624
		625	Lower level Configuration, Coroutine Environment: L<Coro::State>.
		626
		627	Debugging: L<Coro::Debug>.
		628
374	Support/Utility: L<Coro::Cont>, L<Coro::Specific>, L<Coro::State>, L<Coro::Util>.	629	Support/Utility: L<Coro::Specific>, L<Coro::Util>.
375		630
376	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.	631	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.
377		632
378	Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>.	633	Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>.
379		634
		635	Compatibility: L<Coro::LWP>, L<Coro::Storable>, L<Coro::Select>.
		636
380	Embedding: L<Coro:MakeMaker>	637	Embedding: L<Coro:MakeMaker>.
381		638
382	=head1 AUTHOR	639	=head1 AUTHOR
383		640
384	Marc Lehmann <schmorp@schmorp.de>	641	Marc Lehmann <schmorp@schmorp.de>
385	http://home.schmorp.de/	642	http://home.schmorp.de/

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.91 by root, Fri Dec 1 02:17:37 2006 UTC vs. Revision 1.152 by root, Sun Oct 7 13:53:37 2007 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.91 by root, Fri Dec 1 02:17:37 2006 UTC vs.
Revision 1.152 by root, Sun Oct 7 13:53:37 2007 UTC