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

Comparing Coro/Coro.pm (file contents):
Revision 1.142 by root, Tue Oct 2 23:16:24 2007 UTC vs.
Revision 1.180 by root, Fri Apr 25 04:28:50 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 coroutine 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	my $lock = new Coro::Semaphore;
19	cede;	22	my $locked;
		23
		24	$lock->down;
		25	$locked = 1;
		26	$lock->up;
20		27
21	=head1 DESCRIPTION	28	=head1 DESCRIPTION
22		29
23	This module collection manages coroutines. Coroutines are similar	30	This module collection manages coroutines. Coroutines are similar
24	to threads but don't run in parallel at the same time even on SMP	31	to threads but don't run in parallel at the same time even on SMP
…		…
33	is a performance win on Windows machines, and a loss everywhere else).	40	is a performance win on Windows machines, and a loss everywhere else).
34		41
35	In this module, coroutines are defined as "callchain + lexical variables +	42	In this module, coroutines are defined as "callchain + lexical variables +
36	@_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain,	43	@_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain,
37	its own set of lexicals and its own set of perls most important global	44	its own set of lexicals and its own set of perls most important global
38	variables.	45	variables (see L<Coro::State> for more configuration).
39		46
40	=cut	47	=cut
41		48
42	package Coro;	49	package Coro;
43		50
…		…
50		57
51	our $idle; # idle handler	58	our $idle; # idle handler
52	our $main; # main coroutine	59	our $main; # main coroutine
53	our $current; # current coroutine	60	our $current; # current coroutine
54		61
55	our $VERSION = '3.8';	62	our $VERSION = 4.6;
56		63
57	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);	64	our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
58	our %EXPORT_TAGS = (	65	our %EXPORT_TAGS = (
59	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)],
60	);	67	);
61	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));	68	our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready));
62		69
63	{
64	my @async;
65	my $init;
66
67	# this way of handling attributes simply is NOT scalable ;()
68	sub import {
69	no strict 'refs';
70
71	Coro->export_to_level (1, @_);
72
73	my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
74	*{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {
75	my ($package, $ref) = (shift, shift);
76	my @attrs;
77	for (@_) {
78	if ($_ eq "Coro") {
79	push @async, $ref;
80	unless ($init++) {
81	eval q{
82	sub INIT {
83	&async(pop @async) while @async;
84	}
85	};
86	}
87	} else {
88	push @attrs, $_;
89	}
90	}
91	return $old ? $old->($package, $ref, @attrs) : @attrs;
92	};
93	}
94
95	}
96
97	=over 4	70	=over 4
98		71
99	=item $main	72	=item $main
100		73
101	This coroutine represents the main program.	74	This coroutine represents the main program.
…		…
134	This hook is overwritten by modules such as C<Coro::Timer> and	107	This hook is overwritten by modules such as C<Coro::Timer> and
135	C<Coro::Event> to wait on an external event that hopefully wake up a	108	C<Coro::Event> to wait on an external event that hopefully wake up a
136	coroutine so the scheduler can run it.	109	coroutine so the scheduler can run it.
137		110
138	Please note that if your callback recursively invokes perl (e.g. for event	111	Please note that if your callback recursively invokes perl (e.g. for event
139	handlers), then it must be prepared to be called recursively.	112	handlers), then it must be prepared to be called recursively itself.
140		113
141	=cut	114	=cut
142		115
143	$idle = sub {	116	$idle = sub {
144	require Carp;	117	require Carp;
…		…
171	}	144	}
172	};	145	};
173	$manager->desc ("[coro manager]");	146	$manager->desc ("[coro manager]");
174	$manager->prio (PRIO_MAX);	147	$manager->prio (PRIO_MAX);
175		148
176	# static methods. not really.
177
178	=back	149	=back
179		150
180	=head2 STATIC METHODS	151	=head2 STATIC METHODS
181		152
182	Static methods are actually functions that operate on the current coroutine only.	153	Static methods are actually functions that operate on the current coroutine only.
…		…
186	=item async { ... } [@args...]	157	=item async { ... } [@args...]
187		158
188	Create a new asynchronous coroutine and return it's coroutine object	159	Create a new asynchronous coroutine and return it's coroutine object
189	(usually unused). When the sub returns the new coroutine is automatically	160	(usually unused). When the sub returns the new coroutine is automatically
190	terminated.	161	terminated.
		162
		163	See the C<Coro::State::new> constructor for info about the coroutine
		164	environment in which coroutines run.
191		165
192	Calling C<exit> in a coroutine will do the same as calling exit outside	166	Calling C<exit> in a coroutine will do the same as calling exit outside
193	the coroutine. Likewise, when the coroutine dies, the program will exit,	167	the coroutine. Likewise, when the coroutine dies, the program will exit,
194	just as it would in the main program.	168	just as it would in the main program.
195		169
…		…
216	issued in case of an exception instead of terminating the program, as	190	issued in case of an exception instead of terminating the program, as
217	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>	191	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>
218	will not work in the expected way, unless you call terminate or cancel,	192	will not work in the expected way, unless you call terminate or cancel,
219	which somehow defeats the purpose of pooling.	193	which somehow defeats the purpose of pooling.
220		194
221	The priority will be reset to C<0> after each job, otherwise the coroutine	195	The priority will be reset to C<0> after each job, tracing will be
222	will be re-used "as-is".	196	disabled, the description will be reset and the default output filehandle
		197	gets restored, so you can change alkl these. Otherwise the coroutine will
		198	be re-used "as-is": most notably if you change other per-coroutine global
		199	stuff such as C<$/> you need to revert that change, which is most simply
		200	done by using local as in C< local $/ >.
223		201
224	The pool size is limited to 8 idle coroutines (this can be adjusted by	202	The pool size is limited to 8 idle coroutines (this can be adjusted by
225	changing $Coro::POOL_SIZE), and there can be as many non-idle coros as	203	changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
226	required.	204	required.
227		205
…		…
248	_pool_2 $cb;	226	_pool_2 $cb;
249	&schedule;	227	&schedule;
250	}	228	}
251	};	229	};
252		230
253	last if $@ eq "\3terminate\2\n";	231	last if $@ eq "\3async_pool terminate\2\n";
254	warn $@ if $@;	232	warn $@ if $@;
255	}	233	}
256	}	234	}
257		235
258	sub async_pool(&@) {	236	sub async_pool(&@) {
…		…
295		273
296	"Cede" to other coroutines. This function puts the current coroutine into the	274	"Cede" to other coroutines. This function puts the current coroutine into the
297	ready queue and calls C<schedule>, which has the effect of giving up the	275	ready queue and calls C<schedule>, which has the effect of giving up the
298	current "timeslice" to other coroutines of the same or higher priority.	276	current "timeslice" to other coroutines of the same or higher priority.
299		277
300	Returns true if at least one coroutine switch has happened.
301
302	=item Coro::cede_notself	278	=item Coro::cede_notself
303		279
304	Works like cede, but is not exported by default and will cede to any	280	Works like cede, but is not exported by default and will cede to any
305	coroutine, regardless of priority, once.	281	coroutine, regardless of priority, once.
306
307	Returns true if at least one coroutine switch has happened.
308		282
309	=item terminate [arg...]	283	=item terminate [arg...]
310		284
311	Terminates the current coroutine with the given status values (see L<cancel>).	285	Terminates the current coroutine with the given status values (see L<cancel>).
312		286
…		…
329	}	303	}
330	}	304	}
331		305
332	=back	306	=back
333		307
334	# dynamic methods
335
336	=head2 COROUTINE METHODS	308	=head2 COROUTINE METHODS
337		309
338	These are the methods you can call on coroutine objects.	310	These are the methods you can call on coroutine objects.
339		311
340	=over 4	312	=over 4
…		…
344	Create a new coroutine and return it. When the sub returns the coroutine	316	Create a new coroutine and return it. When the sub returns the coroutine
345	automatically terminates as if C<terminate> with the returned values were	317	automatically terminates as if C<terminate> with the returned values were
346	called. To make the coroutine run you must first put it into the ready queue	318	called. To make the coroutine run you must first put it into the ready queue
347	by calling the ready method.	319	by calling the ready method.
348		320
349	See C<async> for additional discussion.	321	See C<async> and C<Coro::State::new> for additional info about the
		322	coroutine environment.
350		323
351	=cut	324	=cut
352		325
353	sub _run_coro {	326	sub _run_coro {
354	terminate &{+shift};	327	terminate &{+shift};
…		…
392	}	365	}
393		366
394	=item $coroutine->join	367	=item $coroutine->join
395		368
396	Wait until the coroutine terminates and return any values given to the	369	Wait until the coroutine terminates and return any values given to the
397	C<terminate> or C<cancel> functions. C<join> can be called multiple times	370	C<terminate> or C<cancel> functions. C<join> can be called concurrently
398	from multiple coroutine.	371	from multiple coroutines.
399		372
400	=cut	373	=cut
401		374
402	sub join {	375	sub join {
403	my $self = shift;	376	my $self = shift;
…		…
462	Sets (or gets in case the argument is missing) the description for this	435	Sets (or gets in case the argument is missing) the description for this
463	coroutine. This is just a free-form string you can associate with a coroutine.	436	coroutine. This is just a free-form string you can associate with a coroutine.
464		437
465	This method simply sets the C<< $coroutine->{desc} >> member to the given string. You	438	This method simply sets the C<< $coroutine->{desc} >> member to the given string. You
466	can modify this member directly if you wish.	439	can modify this member directly if you wish.
		440
		441	=item $coroutine->throw ([$scalar])
		442
		443	If C<$throw> is specified and defined, it will be thrown as an exception
		444	inside the coroutine at the next convinient point in time (usually after
		445	it gains control at the next schedule/transfer/cede). Otherwise clears the
		446	exception object.
		447
		448	The exception object will be thrown "as is" with the specified scalar in
		449	C<$@>, i.e. if it is a string, no line number or newline will be appended
		450	(unlike with C<die>).
		451
		452	This can be used as a softer means than C<cancel> to ask a coroutine to
		453	end itself, although there is no guarentee that the exception will lead to
		454	termination, and if the exception isn't caught it might well end the whole
		455	program.
467		456
468	=cut	457	=cut
469		458
470	sub desc {	459	sub desc {
471	my $old = $_[0]{desc};	460	my $old = $_[0]{desc};
…		…
589	to allow per-thread schedulers, but Coro::State does not yet allow	578	to allow per-thread schedulers, but Coro::State does not yet allow
590	this).	579	this).
591		580
592	=head1 SEE ALSO	581	=head1 SEE ALSO
593		582
		583	Lower level Configuration, Coroutine Environment: L<Coro::State>.
		584
		585	Debugging: L<Coro::Debug>.
		586
594	Support/Utility: L<Coro::Cont>, L<Coro::Specific>, L<Coro::State>, L<Coro::Util>.	587	Support/Utility: L<Coro::Specific>, L<Coro::Util>.
595		588
596	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.	589	Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>.
597		590
598	Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::Select>.	591	Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>.
599		592
		593	Compatibility: L<Coro::LWP>, L<Coro::Storable>, L<Coro::Select>.
		594
600	Embedding: L<Coro:MakeMaker>	595	Embedding: L<Coro::MakeMaker>.
601		596
602	=head1 AUTHOR	597	=head1 AUTHOR
603		598
604	Marc Lehmann <schmorp@schmorp.de>	599	Marc Lehmann <schmorp@schmorp.de>
605	http://home.schmorp.de/	600	http://home.schmorp.de/

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.142 by root, Tue Oct 2 23:16:24 2007 UTC vs. Revision 1.180 by root, Fri Apr 25 04:28:50 2008 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.142 by root, Tue Oct 2 23:16:24 2007 UTC vs.
Revision 1.180 by root, Fri Apr 25 04:28:50 2008 UTC