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

Comparing cvsroot/Coro/Coro.pm (file contents):
Revision 1.92 by root, Fri Dec 1 03:47:55 2006 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 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.6;
47		63
48	our @EXPORT = qw(async cede schedule terminate current unblock_sub);	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
54	{
55	my @async;
56	my $init;
57
58	# this way of handling attributes simply is NOT scalable ;()
59	sub import {
60	no strict 'refs';
61
62	Coro->export_to_level(1, @_);
63
64	my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
65	*{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {
66	my ($package, $ref) = (shift, shift);
67	my @attrs;
68	for (@_) {
69	if ($_ eq "Coro") {
70	push @async, $ref;
71	unless ($init++) {
72	eval q{
73	sub INIT {
74	&async(pop @async) while @async;
75	}
76	};
77	}
78	} else {
79	push @attrs, $_;
80	}
81	}
82	return $old ? $old->($package, $ref, @attrs) : @attrs;
83	};
84	}
85
86	}
87		69
88	=over 4	70	=over 4
89		71
90	=item $main	72	=item $main
91		73
…		…
99		81
100	The current coroutine (the last coroutine switched to). The initial value	82	The current coroutine (the last coroutine switched to). The initial value
101	is C<$main> (of course).	83	is C<$main> (of course).
102		84
103	This variable is B<strictly> I<read-only>. It is provided for performance	85	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	86	reasons. If performance is not essential you are encouraged to use the
105	C<Coro::current> function instead.	87	C<Coro::current> function instead.
106		88
107	=cut	89	=cut
108		90
		91	$main->{desc} = "[main::]";
		92
109	# maybe some other module used Coro::Specific before...	93	# maybe some other module used Coro::Specific before...
110	if ($current) {
111	$main->{specific} = $current->{specific};	94	$main->{_specific} = $current->{_specific}
112	}	95	if $current;
113		96
114	$current = $main;	97	_set_current $main;
115		98
116	sub current() { $current }	99	sub current() { $current }
117		100
118	=item $idle	101	=item $idle
119		102
…		…
124	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
125	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
126	coroutine so the scheduler can run it.	109	coroutine so the scheduler can run it.
127		110
128	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
129	handlers), then it must be prepared to be called recursively.	112	handlers), then it must be prepared to be called recursively itself.
130		113
131	=cut	114	=cut
132		115
133	$idle = sub {	116	$idle = sub {
134	print STDERR "FATAL: deadlock detected\n";	117	require Carp;
135	exit (51);	118	Carp::croak ("FATAL: deadlock detected");
136	};	119	};
		120
		121	sub _cancel {
		122	my ($self) = @_;
		123
		124	# free coroutine data and mark as destructed
		125	$self->_destroy
		126	or return;
		127
		128	# call all destruction callbacks
		129	$_->(@{$self->{_status}})
		130	for @{(delete $self->{_on_destroy}) \|\| []};
		131	}
137		132
138	# this coroutine is necessary because a coroutine	133	# this coroutine is necessary because a coroutine
139	# cannot destroy itself.	134	# cannot destroy itself.
140	my @destroy;	135	my @destroy;
		136	my $manager;
		137
141	my $manager; $manager = new Coro sub {	138	$manager = new Coro sub {
142	while () {	139	while () {
143	# by overwriting the state object with the manager we destroy it	140	(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) {	141	while @destroy;
149	my $coro = pop @destroy;
150	$coro->{status} \|\|= [];
151	$_->ready for @{delete $coro->{join} \|\| []};
152		142
153	# the next line destroys the coro state, but keeps the
154	# coroutine itself intact (we basically make it a zombie
155	# coroutine that always runs the manager thread, so it's possible
156	# to transfer() to this coroutine).
157	$coro->_clone_state_from ($manager);
158	}
159	&schedule;	143	&schedule;
160	}	144	}
161	};	145	};
162		146	$manager->desc ("[coro manager]");
163	# static methods. not really.	147	$manager->prio (PRIO_MAX);
164		148
165	=back	149	=back
166		150
167	=head2 STATIC METHODS	151	=head2 STATIC METHODS
168		152
…		…
174		158
175	Create a new asynchronous coroutine and return it's coroutine object	159	Create a new asynchronous coroutine and return it's coroutine object
176	(usually unused). When the sub returns the new coroutine is automatically	160	(usually unused). When the sub returns the new coroutine is automatically
177	terminated.	161	terminated.
178		162
179	Calling C<exit> in a coroutine will not work correctly, so do not do that.	163	See the C<Coro::State::new> constructor for info about the coroutine
		164	environment in which coroutines run.
180		165
181	When the coroutine dies, the program will exit, just as in the main	166	Calling C<exit> in a coroutine will do the same as calling exit outside
182	program.	167	the coroutine. Likewise, when the coroutine dies, the program will exit,
		168	just as it would in the main program.
183		169
184	# create a new coroutine that just prints its arguments	170	# create a new coroutine that just prints its arguments
185	async {	171	async {
186	print "@_\n";	172	print "@_\n";
187	} 1,2,3,4;	173	} 1,2,3,4;
188		174
189	=cut	175	=cut
190		176
191	sub async(&@) {	177	sub async(&@) {
192	my $pid = new Coro @_;	178	my $coro = new Coro @_;
193	$pid->ready;	179	$coro->ready;
194	$pid	180	$coro
		181	}
		182
		183	=item async_pool { ... } [@args...]
		184
		185	Similar to C<async>, but uses a coroutine pool, so you should not call
		186	terminate or join (although you are allowed to), and you get a coroutine
		187	that might have executed other code already (which can be good or bad :).
		188
		189	Also, the block is executed in an C<eval> context and a warning will be
		190	issued in case of an exception instead of terminating the program, as
		191	C<async> does. As the coroutine is being reused, stuff like C<on_destroy>
		192	will not work in the expected way, unless you call terminate or cancel,
		193	which somehow defeats the purpose of pooling.
		194
		195	The priority will be reset to C<0> after each job, tracing will be
		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 $/ >.
		201
		202	The pool size is limited to 8 idle coroutines (this can be adjusted by
		203	changing $Coro::POOL_SIZE), and there can be as many non-idle coros as
		204	required.
		205
		206	If you are concerned about pooled coroutines growing a lot because a
		207	single C<async_pool> used a lot of stackspace you can e.g. C<async_pool
		208	{ terminate }> once per second or so to slowly replenish the pool. In
		209	addition to that, when the stacks used by a handler grows larger than 16kb
		210	(adjustable with $Coro::POOL_RSS) it will also exit.
		211
		212	=cut
		213
		214	our $POOL_SIZE = 8;
		215	our $POOL_RSS = 16 * 1024;
		216	our @async_pool;
		217
		218	sub pool_handler {
		219	my $cb;
		220
		221	while () {
		222	eval {
		223	while () {
		224	_pool_1 $cb;
		225	&$cb;
		226	_pool_2 $cb;
		227	&schedule;
		228	}
		229	};
		230
		231	last if $@ eq "\3async_pool terminate\2\n";
		232	warn $@ if $@;
		233	}
		234	}
		235
		236	sub async_pool(&@) {
		237	# this is also inlined into the unlock_scheduler
		238	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
		239
		240	$coro->{_invoke} = [@_];
		241	$coro->ready;
		242
		243	$coro
195	}	244	}
196		245
197	=item schedule	246	=item schedule
198		247
199	Calls the scheduler. Please note that the current coroutine will not be put	248	Calls the scheduler. Please note that the current coroutine will not be put
…		…
212	# wake up sleeping coroutine	261	# wake up sleeping coroutine
213	$current->ready;	262	$current->ready;
214	undef $current;	263	undef $current;
215	};	264	};
216		265
217	# call schedule until event occured.	266	# call schedule until event occurred.
218	# in case we are woken up for other reasons	267	# in case we are woken up for other reasons
219	# (current still defined), loop.	268	# (current still defined), loop.
220	Coro::schedule while $current;	269	Coro::schedule while $current;
221	}	270	}
222		271
…		…
224		273
225	"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
226	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
227	current "timeslice" to other coroutines of the same or higher priority.	276	current "timeslice" to other coroutines of the same or higher priority.
228		277
		278	=item Coro::cede_notself
		279
		280	Works like cede, but is not exported by default and will cede to any
		281	coroutine, regardless of priority, once.
		282
229	=item terminate [arg...]	283	=item terminate [arg...]
230		284
231	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>).
		286
		287	=item killall
		288
		289	Kills/terminates/cancels all coroutines except the currently running
		290	one. This is useful after a fork, either in the child or the parent, as
		291	usually only one of them should inherit the running coroutines.
232		292
233	=cut	293	=cut
234		294
235	sub terminate {	295	sub terminate {
236	$current->cancel (@_);	296	$current->cancel (@_);
237	}	297	}
238		298
		299	sub killall {
		300	for (Coro::State::list) {
		301	$_->cancel
		302	if $_ != $current && UNIVERSAL::isa $_, "Coro";
		303	}
		304	}
		305
239	=back	306	=back
240
241	# dynamic methods
242		307
243	=head2 COROUTINE METHODS	308	=head2 COROUTINE METHODS
244		309
245	These are the methods you can call on coroutine objects.	310	These are the methods you can call on coroutine objects.
246		311
…		…
251	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
252	automatically terminates as if C<terminate> with the returned values were	317	automatically terminates as if C<terminate> with the returned values were
253	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
254	by calling the ready method.	319	by calling the ready method.
255		320
256	Calling C<exit> in a coroutine will not work correctly, so do not do that.	321	See C<async> and C<Coro::State::new> for additional info about the
		322	coroutine environment.
257		323
258	=cut	324	=cut
259		325
260	sub _new_coro {	326	sub _run_coro {
261	terminate &{+shift};	327	terminate &{+shift};
262	}	328	}
263		329
264	sub new {	330	sub new {
265	my $class = shift;	331	my $class = shift;
266		332
267	$class->SUPER::new (\&_new_coro, @_)	333	$class->SUPER::new (\&_run_coro, @_)
268	}	334	}
269		335
270	=item $success = $coroutine->ready	336	=item $success = $coroutine->ready
271		337
272	Put the given coroutine into the ready queue (according to it's priority)	338	Put the given coroutine into the ready queue (according to it's priority)
…		…
278	Return wether the coroutine is currently the ready queue or not,	344	Return wether the coroutine is currently the ready queue or not,
279		345
280	=item $coroutine->cancel (arg...)	346	=item $coroutine->cancel (arg...)
281		347
282	Terminates the given coroutine and makes it return the given arguments as	348	Terminates the given coroutine and makes it return the given arguments as
283	status (default: the empty list).	349	status (default: the empty list). Never returns if the coroutine is the
		350	current coroutine.
284		351
285	=cut	352	=cut
286		353
287	sub cancel {	354	sub cancel {
288	my $self = shift;	355	my $self = shift;
289	$self->{status} = [@_];	356	$self->{_status} = [@_];
		357
		358	if ($current == $self) {
290	push @destroy, $self;	359	push @destroy, $self;
291	$manager->ready;	360	$manager->ready;
292	&schedule if $current == $self;	361	&schedule while 1;
		362	} else {
		363	$self->_cancel;
		364	}
293	}	365	}
294		366
295	=item $coroutine->join	367	=item $coroutine->join
296		368
297	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
298	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
299	from multiple coroutine.	371	from multiple coroutines.
300		372
301	=cut	373	=cut
302		374
303	sub join {	375	sub join {
304	my $self = shift;	376	my $self = shift;
		377
305	unless ($self->{status}) {	378	unless ($self->{_status}) {
306	push @{$self->{join}}, $current;	379	my $current = $current;
307	&schedule;	380
		381	push @{$self->{_on_destroy}}, sub {
		382	$current->ready;
		383	undef $current;
		384	};
		385
		386	&schedule while $current;
308	}	387	}
		388
309	wantarray ? @{$self->{status}} : $self->{status}[0];	389	wantarray ? @{$self->{_status}} : $self->{_status}[0];
		390	}
		391
		392	=item $coroutine->on_destroy (\&cb)
		393
		394	Registers a callback that is called when this coroutine gets destroyed,
		395	but before it is joined. The callback gets passed the terminate arguments,
		396	if any.
		397
		398	=cut
		399
		400	sub on_destroy {
		401	my ($self, $cb) = @_;
		402
		403	push @{ $self->{_on_destroy} }, $cb;
310	}	404	}
311		405
312	=item $oldprio = $coroutine->prio ($newprio)	406	=item $oldprio = $coroutine->prio ($newprio)
313		407
314	Sets (or gets, if the argument is missing) the priority of the	408	Sets (or gets, if the argument is missing) the priority of the
…		…
339	=item $olddesc = $coroutine->desc ($newdesc)	433	=item $olddesc = $coroutine->desc ($newdesc)
340		434
341	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
342	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.
343		437
		438	This method simply sets the C<< $coroutine->{desc} >> member to the given string. You
		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.
		456
344	=cut	457	=cut
345		458
346	sub desc {	459	sub desc {
347	my $old = $_[0]{desc};	460	my $old = $_[0]{desc};
348	$_[0]{desc} = $_[1] if @_ > 1;	461	$_[0]{desc} = $_[1] if @_ > 1;
349	$old;	462	$old;
350	}	463	}
351		464
352	=back	465	=back
353		466
354	=head2 UTILITY FUNCTIONS	467	=head2 GLOBAL FUNCTIONS
355		468
356	=over 4	469	=over 4
		470
		471	=item Coro::nready
		472
		473	Returns the number of coroutines that are currently in the ready state,
		474	i.e. that can be switched to. The value C<0> means that the only runnable
		475	coroutine is the currently running one, so C<cede> would have no effect,
		476	and C<schedule> would cause a deadlock unless there is an idle handler
		477	that wakes up some coroutines.
		478
		479	=item my $guard = Coro::guard { ... }
		480
		481	This creates and returns a guard object. Nothing happens until the object
		482	gets destroyed, in which case the codeblock given as argument will be
		483	executed. This is useful to free locks or other resources in case of a
		484	runtime error or when the coroutine gets canceled, as in both cases the
		485	guard block will be executed. The guard object supports only one method,
		486	C<< ->cancel >>, which will keep the codeblock from being executed.
		487
		488	Example: set some flag and clear it again when the coroutine gets canceled
		489	or the function returns:
		490
		491	sub do_something {
		492	my $guard = Coro::guard { $busy = 0 };
		493	$busy = 1;
		494
		495	# do something that requires $busy to be true
		496	}
		497
		498	=cut
		499
		500	sub guard(&) {
		501	bless \(my $cb = $_[0]), "Coro::guard"
		502	}
		503
		504	sub Coro::guard::cancel {
		505	${$_[0]} = sub { };
		506	}
		507
		508	sub Coro::guard::DESTROY {
		509	${$_[0]}->();
		510	}
		511
357		512
358	=item unblock_sub { ... }	513	=item unblock_sub { ... }
359		514
360	This utility function takes a BLOCK or code reference and "unblocks" it,	515	This utility function takes a BLOCK or code reference and "unblocks" it,
361	returning the new coderef. This means that the new coderef will return	516	returning the new coderef. This means that the new coderef will return
362	immediately without blocking, returning nothing, while the original code	517	immediately without blocking, returning nothing, while the original code
363	ref will be called (with parameters) from within its own coroutine.	518	ref will be called (with parameters) from within its own coroutine.
364		519
365	The reason this fucntion exists is that many event libraries (such as the	520	The reason this function exists is that many event libraries (such as the
366	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form	521	venerable L<Event\|Event> module) are not coroutine-safe (a weaker form
367	of thread-safety). This means you must not block within event callbacks,	522	of thread-safety). This means you must not block within event callbacks,
368	otherwise you might suffer from crashes or worse.	523	otherwise you might suffer from crashes or worse.
369		524
370	This function allows your callbacks to block by executing them in another	525	This function allows your callbacks to block by executing them in another
…		…
375	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when	530	In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when
376	creating event callbacks that want to block.	531	creating event callbacks that want to block.
377		532
378	=cut	533	=cut
379		534
380	our @unblock_pool;
381	our @unblock_queue;	535	our @unblock_queue;
382	our $UNBLOCK_POOL_SIZE = 2;
383		536
384	sub unblock_handler_ {	537	# we create a special coro because we want to cede,
385	while () {	538	# to reduce pressure on the coro pool (because most callbacks
386	my ($cb, @arg) = @{ delete $Coro::current->{arg} };	539	# return immediately and can be reused) and because we cannot cede
387	$cb->(@arg);	540	# inside an event callback.
388
389	last if @unblock_pool >= $UNBLOCK_POOL_SIZE;
390	push @unblock_pool, $Coro::current;
391	schedule;
392	}
393	}
394
395	our $unblock_scheduler = async {	541	our $unblock_scheduler = new Coro sub {
396	while () {	542	while () {
397	while (my $cb = pop @unblock_queue) {	543	while (my $cb = pop @unblock_queue) {
398	my $handler = (pop @unblock_pool or new Coro \&unblock_handler_);	544	# this is an inlined copy of async_pool
399	$handler->{arg} = $cb;	545	my $coro = (pop @async_pool) \|\| new Coro \&pool_handler;
		546
		547	$coro->{_invoke} = $cb;
400	$handler->ready;	548	$coro->ready;
401	cede;	549	cede; # for short-lived callbacks, this reduces pressure on the coro pool
402	}	550	}
403		551	schedule; # sleep well
404	schedule;
405	}	552	}
406	};	553	};
		554	$unblock_scheduler->desc ("[unblock_sub scheduler]");
407		555
408	sub unblock_sub(&) {	556	sub unblock_sub(&) {
409	my $cb = shift;	557	my $cb = shift;
410		558
411	sub {	559	sub {
412	push @unblock_queue, [$cb, @_];	560	unshift @unblock_queue, [$cb, @_];
413	$unblock_scheduler->ready;	561	$unblock_scheduler->ready;
414	}	562	}
415	}	563	}
416		564
417	=back	565	=back
…		…
424		572
425	- you must make very sure that no coro is still active on global	573	- you must make very sure that no coro is still active on global
426	destruction. very bad things might happen otherwise (usually segfaults).	574	destruction. very bad things might happen otherwise (usually segfaults).
427		575
428	- this module is not thread-safe. You should only ever use this module	576	- this module is not thread-safe. You should only ever use this module
429	from the same thread (this requirement might be losened in the future	577	from the same thread (this requirement might be loosened in the future
430	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
431	this).	579	this).
432		580
433	=head1 SEE ALSO	581	=head1 SEE ALSO
434		582
		583	Lower level Configuration, Coroutine Environment: L<Coro::State>.
		584
		585	Debugging: L<Coro::Debug>.
		586
435	Support/Utility: L<Coro::Cont>, L<Coro::Specific>, L<Coro::State>, L<Coro::Util>.	587	Support/Utility: L<Coro::Specific>, L<Coro::Util>.
436		588
437	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>.
438		590
439	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>.
440		592
		593	Compatibility: L<Coro::LWP>, L<Coro::Storable>, L<Coro::Select>.
		594
441	Embedding: L<Coro:MakeMaker>	595	Embedding: L<Coro::MakeMaker>.
442		596
443	=head1 AUTHOR	597	=head1 AUTHOR
444		598
445	Marc Lehmann <schmorp@schmorp.de>	599	Marc Lehmann <schmorp@schmorp.de>
446	http://home.schmorp.de/	600	http://home.schmorp.de/

Diff Legend

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

Comparing cvsroot/Coro/Coro.pm (file contents): Revision 1.92 by root, Fri Dec 1 03:47:55 2006 UTC vs. Revision 1.180 by root, Fri Apr 25 04:28:50 2008 UTC

Diff Legend

Comparing cvsroot/Coro/Coro.pm (file contents):
Revision 1.92 by root, Fri Dec 1 03:47:55 2006 UTC vs.
Revision 1.180 by root, Fri Apr 25 04:28:50 2008 UTC