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

Comparing Coro/Coro.pm (file contents):
Revision 1.25 by root, Wed Jul 25 21:12:57 2001 UTC vs.
Revision 1.35 by root, Mon Sep 24 00:16:30 2001 UTC

36 36
37use Coro::State; 37use Coro::State;
38 38
39use base Exporter; 39use base Exporter;
40 40
41$VERSION = 0.12; 41$VERSION = 0.5;
42 42
43@EXPORT = qw(async cede schedule terminate current); 43@EXPORT = qw(async cede schedule terminate current);
44@EXPORT_OK = qw($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}};
45 48
46{ 49{
47 my @async; 50 my @async;
51 my $init;
48 52
49 # this way of handling attributes simply is NOT scalable ;() 53 # this way of handling attributes simply is NOT scalable ;()
50 sub import { 54 sub import {
51 Coro->export_to_level(1, @_); 55 Coro->export_to_level(1, @_);
52 my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE}; 56 my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
54 my ($package, $ref) = (shift, shift); 58 my ($package, $ref) = (shift, shift);
55 my @attrs; 59 my @attrs;
56 for (@_) { 60 for (@_) {
57 if ($_ eq "Coro") { 61 if ($_ eq "Coro") {
58 push @async, $ref; 62 push @async, $ref;
63 unless ($init++) {
64 eval q{
65 sub INIT {
66 &async(pop @async) while @async;
67 }
68 };
69 }
59 } else { 70 } else {
60 push @attrs, $_; 71 push @attrs, $_;
61 } 72 }
62 } 73 }
63 return $old ? $old->($package, $ref, @attrs) : @attrs; 74 return $old ? $old->($package, $ref, @attrs) : @attrs;
64 }; 75 };
65 } 76 }
66 77
67 sub INIT {
68 &async(pop @async) while @async;
69 }
70} 78}
71 79
72=item $main 80=item $main
73 81
74This coroutine represents the main program. 82This coroutine represents the main program.
113 delete ((pop @destroy)->{_coro_state}) while @destroy; 121 delete ((pop @destroy)->{_coro_state}) while @destroy;
114 &schedule; 122 &schedule;
115 } 123 }
116}; 124};
117 125
118# we really need priorities...
119my @ready; # the ready queue. hehe, rather broken ;)
120
121# static methods. not really. 126# static methods. not really.
122 127
123=head2 STATIC METHODS 128=head2 STATIC METHODS
124 129
125Static methods are actually functions that operate on the current process only. 130Static methods are actually functions that operate on the current process only.
155into the ready queue, so calling this function usually means you will 160into the ready queue, so calling this function usually means you will
156never be called again. 161never be called again.
157 162
158=cut 163=cut
159 164
160my $prev;
161
162sub schedule {
163 # should be done using priorities :(
164 ($prev, $current) = ($current, shift @ready || $idle);
165 Coro::State::transfer($prev, $current);
166}
167
168=item cede 165=item cede
169 166
170"Cede" to other processes. This function puts the current process into the 167"Cede" to other processes. This function puts the current process into the
171ready queue and calls C<schedule>, which has the effect of giving up the 168ready queue and calls C<schedule>, which has the effect of giving up the
172current "timeslice" to other coroutines of the same or higher priority. 169current "timeslice" to other coroutines of the same or higher priority.
173 170
174=cut 171=cut
175 172
176sub cede { 173=item terminate
174
175Terminates the current process.
176
177Future versions of this function will allow result arguments.
178
179=cut
180
181sub terminate {
177 $current->ready; 182 $current->cancel;
178 &schedule; 183 &schedule;
179}
180
181=item terminate
182
183Terminates the current process.
184
185Future versions of this function will allow result arguments.
186
187=cut
188
189sub terminate {
190 push @destroy, $current;
191 $manager->ready;
192 &schedule;
193 # NORETURN 184 die; # NORETURN
194} 185}
195 186
196=back 187=back
197 188
198# dynamic methods 189# dynamic methods
229 220
230Put the current process into the ready queue. 221Put the current process into the ready queue.
231 222
232=cut 223=cut
233 224
234sub ready { 225=item $process->cancel
226
227Like C<terminate>, but terminates the specified process instead.
228
229=cut
230
231sub cancel {
235 push @ready, $_[0]; 232 push @destroy, $_[0];
233 $manager->ready;
234 &schedule if $current == $_[0];
235}
236
237=item $oldprio = $process->prio($newprio)
238
239Sets the priority of the process. Higher priority processes get run before
240lower priority processes. Priorities are smalled signed integer (currently
241-4 .. +3), that you can refer to using PRIO_xxx constants (use the import
242tag :prio to get then):
243
244 PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
245 3 > 1 > 0 > -1 > -3 > -4
246
247 # set priority to HIGH
248 current->prio(PRIO_HIGH);
249
250The idle coroutine ($Coro::idle) always has a lower priority than any
251existing coroutine.
252
253Changing the priority of the current process will take effect immediately,
254but changing the priority of processes in the ready queue (but not
255running) will only take effect after the next schedule (of that
256process). This is a bug that will be fixed in some future version.
257
258=cut
259
260sub prio {
261 my $old = $_[0]{prio};
262 $_[0]{prio} = $_[1] if @_ > 1;
263 $old;
264}
265
266=item $newprio = $process->nice($change)
267
268Similar to C<prio>, but subtract the given value from the priority (i.e.
269higher values mean lower priority, just as in unix).
270
271=cut
272
273sub nice {
274 $_[0]{prio} -= $_[1];
236} 275}
237 276
238=back 277=back
239 278
240=cut 279=cut
241 280
2421; 2811;
243 282
244=head1 BUGS/LIMITATIONS 283=head1 BUGS/LIMITATIONS
245 284
246 - could be faster, especially when the core would introduce special 285 - you must make very sure that no coro is still active on global destruction.
247 support for coroutines (like it does for threads). 286 very bad things might happen otherwise (usually segfaults).
248 - there is still a memleak on coroutine termination that I could not
249 identify. Could be as small as a single SV.
250 - this module is not well-tested.
251 - if variables or arguments "disappear" (become undef) or become
252 corrupted please contact the author so he cen iron out the
253 remaining bugs.
254 - this module is not thread-safe. You must only ever use this module from 287 - this module is not thread-safe. You must only ever use this module from
255 the same thread (this requirement might be loosened in the future to 288 the same thread (this requirement might be loosened in the future to
256 allow per-thread schedulers, but Coro::State does not yet allow this). 289 allow per-thread schedulers, but Coro::State does not yet allow this).
257 290
258=head1 SEE ALSO 291=head1 SEE ALSO
259 292
260L<Coro::Channel>, L<Coro::Cont>, L<Coro::Specific>, L<Coro::Semaphore>, 293L<Coro::Channel>, L<Coro::Cont>, L<Coro::Specific>, L<Coro::Semaphore>,
261L<Coro::Signal>, L<Coro::State>, L<Coro::Event>, L<Coro::RWLock>, 294L<Coro::Signal>, L<Coro::State>, L<Coro::Event>, L<Coro::RWLock>,
262L<Coro::L<Coro::Handle>, L<Coro::Socket>. 295L<Coro::Handle>, L<Coro::Socket>.
263 296
264=head1 AUTHOR 297=head1 AUTHOR
265 298
266 Marc Lehmann <pcg@goof.com> 299 Marc Lehmann <pcg@goof.com>
267 http://www.goof.com/pcg/marc/ 300 http://www.goof.com/pcg/marc/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines