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

Comparing Coro/Coro.pm (file contents):
Revision 1.23 by root, Mon Jul 23 04:23:32 2001 UTC vs.
Revision 1.53 by root, Tue May 27 01:15:26 2003 UTC

…		…
19	cede;	19	cede;
20		20
21	=head1 DESCRIPTION	21	=head1 DESCRIPTION
22		22
23	This module collection manages coroutines. Coroutines are similar to	23	This module collection manages coroutines. Coroutines are similar to
24	Threads but don't run in parallel.	24	threads but don't run in parallel.
25
26	This module is still experimental, see the BUGS section below.
27		25
28	In this module, coroutines are defined as "callchain + lexical variables	26	In this module, coroutines are defined as "callchain + lexical variables
29	+ @_ + $_ + $@ + $^W + C stack), that is, a coroutine has it's own	27	+ @_ + $_ + $@ + $^W + C stack), that is, a coroutine has it's own
30	callchain, it's own set of lexicals and it's own set of perl's most	28	callchain, it's own set of lexicals and it's own set of perl's most
31	important global variables.	29	important global variables.
32		30
33	=cut	31	=cut
34		32
35	package Coro;	33	package Coro;
36		34
		35	no warnings qw(uninitialized);
		36
37	use Coro::State;	37	use Coro::State;
38		38
39	use base Exporter;	39	use base Exporter;
40		40
41	$VERSION = 0.10;	41	$VERSION = 0.7;
42		42
43	@EXPORT = qw(async cede schedule terminate current);	43	@EXPORT = qw(async cede schedule terminate current);
44	@EXPORT_OK = qw($current);	44	%EXPORT_TAGS = (
		45	prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
		46	);
		47	@EXPORT_OK = @{$EXPORT_TAGS{prio}};
45		48
46	{	49	{
47	my @async;	50	my @async;
		51	my $init;
48		52
49	# this way of handling attributes simply is NOT scalable ;()	53	# this way of handling attributes simply is NOT scalable ;()
50	sub import {	54	sub import {
51	Coro->export_to_level(1, @_);	55	Coro->export_to_level(1, @_);
52	my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};	56	my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
…		…
54	my ($package, $ref) = (shift, shift);	58	my ($package, $ref) = (shift, shift);
55	my @attrs;	59	my @attrs;
56	for (@_) {	60	for (@_) {
57	if ($_ eq "Coro") {	61	if ($_ eq "Coro") {
58	push @async, $ref;	62	push @async, $ref;
		63	unless ($init++) {
		64	eval q{
		65	sub INIT {
		66	&async(pop @async) while @async;
		67	}
		68	};
		69	}
59	} else {	70	} else {
60	push @attrs, $_;	71	push @attrs, $_;
61	}	72	}
62	}	73	}
63	return $old ? $old->($package, $ref, @attrs) : @attrs;	74	return $old ? $old->($package, $ref, @attrs) : @attrs;
64	};	75	};
65	}	76	}
66		77
67	sub INIT {
68	&async(pop @async) while @async;
69	}
70	}	78	}
		79
		80	=over 4
71		81
72	=item $main	82	=item $main
73		83
74	This coroutine represents the main program.	84	This coroutine represents the main program.
75		85
…		…
103	our $idle = new Coro sub {	113	our $idle = new Coro sub {
104	print STDERR "FATAL: deadlock detected\n";	114	print STDERR "FATAL: deadlock detected\n";
105	exit(51);	115	exit(51);
106	};	116	};
107		117
108	# we really need priorities...	118	# this coroutine is necessary because a coroutine
109	my @ready; # the ready queue. hehe, rather broken ;)	119	# cannot destroy itself.
		120	my @destroy;
		121	my $manager;
		122	$manager = new Coro sub {
		123	while() {
		124	# by overwriting the state object with the manager we destroy it
		125	# while still being able to schedule this coroutine (in case it has
		126	# been readied multiple times. this is harmless since the manager
		127	# can be called as many times as neccessary and will always
		128	# remove itself from the runqueue
		129	while (@destroy) {
		130	my $coro = pop @destroy;
		131	$coro->{status} \|\|= [];
		132	$_->ready for @{delete $coro->{join} \|\| []};
		133	$coro->{_coro_state} = $manager->{_coro_state};
		134	}
		135	&schedule;
		136	}
		137	};
110		138
111	# static methods. not really.	139	# static methods. not really.
		140
		141	=back
112		142
113	=head2 STATIC METHODS	143	=head2 STATIC METHODS
114		144
115	Static methods are actually functions that operate on the current process only.	145	Static methods are actually functions that operate on the current process only.
116		146
…		…
132		162
133	=cut	163	=cut
134		164
135	sub async(&@) {	165	sub async(&@) {
136	my $pid = new Coro @_;	166	my $pid = new Coro @_;
		167	$manager->ready; # this ensures that the stack is cloned from the manager
137	$pid->ready;	168	$pid->ready;
138	$pid;	169	$pid;
139	}	170	}
140		171
141	=item schedule	172	=item schedule
…		…
144	into the ready queue, so calling this function usually means you will	175	into the ready queue, so calling this function usually means you will
145	never be called again.	176	never be called again.
146		177
147	=cut	178	=cut
148		179
149	my $prev;
150
151	sub schedule {
152	# should be done using priorities :(
153	($prev, $current) = ($current, shift @ready \|\| $idle);
154	Coro::State::transfer($prev, $current);
155	}
156
157	=item cede	180	=item cede
158		181
159	"Cede" to other processes. This function puts the current process into the	182	"Cede" to other processes. This function puts the current process into the
160	ready queue and calls C<schedule>, which has the effect of giving up the	183	ready queue and calls C<schedule>, which has the effect of giving up the
161	current "timeslice" to other coroutines of the same or higher priority.	184	current "timeslice" to other coroutines of the same or higher priority.
162		185
163	=cut	186	=cut
164		187
165	sub cede {	188	=item terminate [arg...]
		189
		190	Terminates the current process.
		191
		192	Future versions of this function will allow result arguments.
		193
		194	=cut
		195
		196	sub terminate {
		197	$current->{status} = [@_];
166	$current->ready;	198	$current->cancel;
167	&schedule;	199	&schedule;
168	}
169
170	=item terminate
171
172	Terminates the current process.
173
174	Future versions of this function will allow result arguments.
175
176	=cut
177
178	# this coroutine is necessary because a coroutine
179	# cannot destroy itself.
180	my @destroy;
181	my $terminate = new Coro sub {
182	while() {
183	delete ((pop @destroy)->{_coro_state}) while @destroy;
184	&schedule;
185	}
186	};
187
188	sub terminate {
189	push @destroy, $current;
190	$terminate->ready;
191	&schedule;
192	# NORETURN	200	die; # NORETURN
193	}	201	}
194		202
195	=back	203	=back
196		204
197	# dynamic methods	205	# dynamic methods
…		…
203	=over 4	211	=over 4
204		212
205	=item new Coro \&sub [, @args...]	213	=item new Coro \&sub [, @args...]
206		214
207	Create a new process and return it. When the sub returns the process	215	Create a new process and return it. When the sub returns the process
208	automatically terminates. To start the process you must first put it into	216	automatically terminates as if C<terminate> with the returned values were
		217	called. To make the process run you must first put it into the ready queue
209	the ready queue by calling the ready method.	218	by calling the ready method.
210
211	The coderef you submit MUST NOT be a closure that refers to variables
212	in an outer scope. This does NOT work. Pass arguments into it instead.
213		219
214	=cut	220	=cut
215		221
216	sub _newcoro {	222	sub _newcoro {
217	terminate &{+shift};	223	terminate &{+shift};
…		…
224	}, $class;	230	}, $class;
225	}	231	}
226		232
227	=item $process->ready	233	=item $process->ready
228		234
229	Put the current process into the ready queue.	235	Put the given process into the ready queue.
230		236
231	=cut	237	=cut
232		238
233	sub ready {	239	=item $process->cancel
		240
		241	Like C<terminate>, but terminates the specified process instead.
		242
		243	=cut
		244
		245	sub cancel {
234	push @ready, $_[0];	246	push @destroy, $_[0];
		247	$manager->ready;
		248	&schedule if $current == $_[0];
		249	}
		250
		251	=item $process->join
		252
		253	Wait until the coroutine terminates and return any values given to the
		254	C<terminate> function. C<join> can be called multiple times from multiple
		255	processes.
		256
		257	=cut
		258
		259	sub join {
		260	my $self = shift;
		261	unless ($self->{status}) {
		262	push @{$self->{join}}, $current;
		263	&schedule;
		264	}
		265	wantarray ? @{$self->{status}} : $self->{status}[0];
		266	}
		267
		268	=item $oldprio = $process->prio($newprio)
		269
		270	Sets (or gets, if the argument is missing) the priority of the
		271	process. Higher priority processes get run before lower priority
		272	processes. Priorities are small signed integers (currently -4 .. +3),
		273	that you can refer to using PRIO_xxx constants (use the import tag :prio
		274	to get then):
		275
		276	PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
		277	3 > 1 > 0 > -1 > -3 > -4
		278
		279	# set priority to HIGH
		280	current->prio(PRIO_HIGH);
		281
		282	The idle coroutine ($Coro::idle) always has a lower priority than any
		283	existing coroutine.
		284
		285	Changing the priority of the current process will take effect immediately,
		286	but changing the priority of processes in the ready queue (but not
		287	running) will only take effect after the next schedule (of that
		288	process). This is a bug that will be fixed in some future version.
		289
		290	=cut
		291
		292	sub prio {
		293	my $old = $_[0]{prio};
		294	$_[0]{prio} = $_[1] if @_ > 1;
		295	$old;
		296	}
		297
		298	=item $newprio = $process->nice($change)
		299
		300	Similar to C<prio>, but subtract the given value from the priority (i.e.
		301	higher values mean lower priority, just as in unix).
		302
		303	=cut
		304
		305	sub nice {
		306	$_[0]{prio} -= $_[1];
		307	}
		308
		309	=item $olddesc = $process->desc($newdesc)
		310
		311	Sets (or gets in case the argument is missing) the description for this
		312	process. This is just a free-form string you can associate with a process.
		313
		314	=cut
		315
		316	sub desc {
		317	my $old = $_[0]{desc};
		318	$_[0]{desc} = $_[1] if @_ > 1;
		319	$old;
235	}	320	}
236		321
237	=back	322	=back
238		323
239	=cut	324	=cut
240		325
241	1;	326	1;
242		327
243	=head1 BUGS/LIMITATIONS	328	=head1 BUGS/LIMITATIONS
244		329
245	- could be faster, especially when the core would introduce special	330	- you must make very sure that no coro is still active on global
246	support for coroutines (like it does for threads).	331	destruction. very bad things might happen otherwise (usually segfaults).
247	- there is still a memleak on coroutine termination that I could not	332
248	identify. Could be as small as a single SV.
249	- this module is not well-tested.
250	- if variables or arguments "disappear" (become undef) or become
251	corrupted please contact the author so he cen iron out the
252	remaining bugs.
253	- this module is not thread-safe. You must only ever use this module from	333	- this module is not thread-safe. You should only ever use this module
254	the same thread (this requirement might be loosened in the future to	334	from the same thread (this requirement might be losened in the future
255	allow per-thread schedulers, but Coro::State does not yet allow this).	335	to allow per-thread schedulers, but Coro::State does not yet allow
		336	this).
256		337
257	=head1 SEE ALSO	338	=head1 SEE ALSO
258		339
259	L<Coro::Channel>, L<Coro::Cont>, L<Coro::Specific>, L<Coro::Semaphore>,	340	L<Coro::Channel>, L<Coro::Cont>, L<Coro::Specific>, L<Coro::Semaphore>,
260	L<Coro::Signal>, L<Coro::State>, L<Coro::Event>.	341	L<Coro::Signal>, L<Coro::State>, L<Coro::Event>, L<Coro::RWLock>,
		342	L<Coro::Handle>, L<Coro::Socket>.
261		343
262	=head1 AUTHOR	344	=head1 AUTHOR
263		345
264	Marc Lehmann <pcg@goof.com>	346	Marc Lehmann <pcg@goof.com>
265	http://www.goof.com/pcg/marc/	347	http://www.goof.com/pcg/marc/

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.23 by root, Mon Jul 23 04:23:32 2001 UTC vs. Revision 1.53 by root, Tue May 27 01:15:26 2003 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.23 by root, Mon Jul 23 04:23:32 2001 UTC vs.
Revision 1.53 by root, Tue May 27 01:15:26 2003 UTC