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

Comparing cvsroot/Coro/Coro.pm (file contents):
Revision 1.30 by root, Sat Aug 11 19:59:19 2001 UTC vs.
Revision 1.37 by root, Mon Sep 24 02:25:44 2001 UTC

… …
32 32
33=cut 33=cut
34 34
35package Coro; 35package Coro;
36 36
37no warnings qw(uninitialized);
38
37use Coro::State; 39use Coro::State;
38 40
39use base Exporter; 41use base Exporter;
40 42
41$VERSION = 0.45; 43$VERSION = 0.5;
42 44
43@EXPORT = qw(async cede schedule terminate current); 45@EXPORT = qw(async cede schedule terminate current);
44@EXPORT_OK = qw($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}};
45 50
46{ 51{
47 my @async; 52 my @async;
48 my $init; 53 my $init;
49 54
… …
113# this coroutine is necessary because a coroutine 118# this coroutine is necessary because a coroutine
114# cannot destroy itself. 119# cannot destroy itself.
115my @destroy; 120my @destroy;
116my $manager = new Coro sub { 121my $manager = new Coro sub {
117 while() { 122 while() {
118 delete ((pop @destroy)->{_coro_state}) while @destroy; 123 # by overwriting the state object with the manager we destroy it
124 # while still being able to schedule this coroutine (in case it has
125 # been readied multiple times. this is harmless since the manager
126 # can be called as many times as neccessary and will always
127 # remove itself from the runqueue
128 (pop @destroy)->{_coro_state} = $manager->{_coro_state} while @destroy;
119 &schedule; 129 &schedule;
120 } 130 }
121}; 131};
122 132
123# static methods. not really. 133# static methods. not really.
… …
226=cut 236=cut
227 237
228sub cancel { 238sub cancel {
229 push @destroy, $_[0]; 239 push @destroy, $_[0];
230 $manager->ready; 240 $manager->ready;
241 &schedule if $current == $_[0];
242}
243
244=item $oldprio = $process->prio($newprio)
245
246Sets the priority of the process. Higher priority processes get run before
247lower priority processes. Priorities are smalled signed integer (currently
248-4 .. +3), that you can refer to using PRIO_xxx constants (use the import
249tag :prio to get then):
250
251 PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
252 3 > 1 > 0 > -1 > -3 > -4
253
254 # set priority to HIGH
255 current->prio(PRIO_HIGH);
256
257The idle coroutine ($Coro::idle) always has a lower priority than any
258existing coroutine.
259
260Changing the priority of the current process will take effect immediately,
261but changing the priority of processes in the ready queue (but not
262running) will only take effect after the next schedule (of that
263process). This is a bug that will be fixed in some future version.
264
265=cut
266
267sub prio {
268 my $old = $_[0]{prio};
269 $_[0]{prio} = $_[1] if @_ > 1;
270 $old;
271}
272
273=item $newprio = $process->nice($change)
274
275Similar to C<prio>, but subtract the given value from the priority (i.e.
276higher values mean lower priority, just as in unix).
277
278=cut
279
280sub nice {
281 $_[0]{prio} -= $_[1];
231} 282}
232 283
233=back 284=back
234 285
235=cut 286=cut
236 287
2371; 2881;
238 289
239=head1 BUGS/LIMITATIONS 290=head1 BUGS/LIMITATIONS
240 291
241 - could be faster, especially when the core would introduce special 292 - you must make very sure that no coro is still active on global destruction.
242 support for coroutines (like it does for threads). 293 very bad things might happen otherwise (usually segfaults).
243 - there is still a memleak on coroutine termination that I could not
244 identify. Could be as small as a single SV.
245 - this module is not well-tested.
246 - if variables or arguments "disappear" (become undef) or become
247 corrupted please contact the author so he cen iron out the
248 remaining bugs.
249 - this module is not thread-safe. You must only ever use this module from 294 - this module is not thread-safe. You must only ever use this module from
250 the same thread (this requirement might be loosened in the future to 295 the same thread (this requirement might be loosened in the future to
251 allow per-thread schedulers, but Coro::State does not yet allow this). 296 allow per-thread schedulers, but Coro::State does not yet allow this).
252 297
253=head1 SEE ALSO 298=head1 SEE ALSO

Diff Legend

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