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

Comparing Coro/Coro.pm (file contents):
Revision 1.80 by root, Mon Nov 6 19:56:26 2006 UTC vs.
Revision 1.137 by root, Wed Sep 26 19:26:48 2007 UTC

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

Diff Legend

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

Comparing Coro/Coro.pm (file contents): Revision 1.80 by root, Mon Nov 6 19:56:26 2006 UTC vs. Revision 1.137 by root, Wed Sep 26 19:26:48 2007 UTC

Diff Legend

Comparing Coro/Coro.pm (file contents):
Revision 1.80 by root, Mon Nov 6 19:56:26 2006 UTC vs.
Revision 1.137 by root, Wed Sep 26 19:26:48 2007 UTC