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

Comparing Coro/Coro.pm (file contents):
Revision 1.22 by root, Mon Jul 23 02:14:19 2001 UTC vs.
Revision 1.88 by root, Sun Nov 26 02:54:55 2006 UTC

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines