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

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

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines