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

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines