ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/Coro/Coro.pm
(Generate patch)

Comparing Coro/Coro.pm (file contents):
Revision 1.5 by root, Tue Jul 10 01:43:21 2001 UTC vs.
Revision 1.56 by pcg, Sat Nov 15 03:53:10 2003 UTC

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

Diff Legend

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