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

Comparing Coro/Coro.pm (file contents):
Revision 1.29 by root, Sat Aug 11 00:37:31 2001 UTC vs.
Revision 1.33 by root, Sun Sep 16 00:44:05 2001 UTC

… …
36 36
37use Coro::State; 37use Coro::State;
38 38
39use base Exporter; 39use base Exporter;
40 40
41$VERSION = 0.45; 41$VERSION = 0.49;
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;
48 my $init; 51 my $init;
49 52
… …
118 delete ((pop @destroy)->{_coro_state}) while @destroy; 121 delete ((pop @destroy)->{_coro_state}) while @destroy;
119 &schedule; 122 &schedule;
120 } 123 }
121}; 124};
122 125
123# we really need priorities...
124my @ready; # the ready queue. hehe, rather broken ;)
125
126# static methods. not really. 126# static methods. not really.
127 127
128=head2 STATIC METHODS 128=head2 STATIC METHODS
129 129
130Static methods are actually functions that operate on the current process only. 130Static methods are actually functions that operate on the current process only.
… …
160into the ready queue, so calling this function usually means you will 160into the ready queue, so calling this function usually means you will
161never be called again. 161never be called again.
162 162
163=cut 163=cut
164 164
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 165=item cede
174 166
175"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
176ready 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
177current "timeslice" to other coroutines of the same or higher priority. 169current "timeslice" to other coroutines of the same or higher priority.
178 170
179=cut 171=cut
180
181sub cede {
182 $current->ready;
183 &schedule;
184}
185 172
186=item terminate 173=item terminate
187 174
188Terminates the current process. 175Terminates the current process.
189 176
… …
233 220
234Put the current process into the ready queue. 221Put the current process into the ready queue.
235 222
236=cut 223=cut
237 224
238sub ready {
239 push @ready, $_[0];
240}
241
242=item $process->cancel 225=item $process->cancel
243 226
244Like C<terminate>, but terminates the specified process instead. 227Like C<terminate>, but terminates the specified process instead.
245 228
246=cut 229=cut
… …
248sub cancel { 231sub cancel {
249 push @destroy, $_[0]; 232 push @destroy, $_[0];
250 $manager->ready; 233 $manager->ready;
251} 234}
252 235
236=item $oldprio = $process->prio($newprio)
237
238Sets the priority of the process. Higher priority processes get run before
239lower priority processes. Priorities are smalled signed integer (currently
240-4 .. +3), that you can refer to using PRIO_xxx constants (use the import
241tag :prio to get then):
242
243 PRIO_MAX > PRIO_HIGH > PRIO_NORMAL > PRIO_LOW > PRIO_IDLE > PRIO_MIN
244 3 > 1 > 0 > -1 > -3 > -4
245
246 # set priority to HIGH
247 current->prio(PRIO_HIGH);
248
249The idle coroutine ($Coro::idle) always has a lower priority than any
250existing coroutine.
251
252Changing the priority of the current process will take effect immediately,
253but changing the priority of processes in the ready queue (but not
254running) will only take effect after the next schedule (of that
255process). This is a bug that will be fixed in some future version.
256
257=cut
258
259sub prio {
260 my $old = $_[0]{prio};
261 $_[0]{prio} = $_[1] if @_ > 1;
262 $old;
263}
264
265=item $newprio = $process->nice($change)
266
267Similar to C<prio>, but subtract the given value from the priority (i.e.
268higher values mean lower priority, just as in unix).
269
270=cut
271
272sub nice {
273 $_[0]{prio} -= $_[1];
274}
275
253=back 276=back
254 277
255=cut 278=cut
256 279
2571; 2801;
258 281
259=head1 BUGS/LIMITATIONS 282=head1 BUGS/LIMITATIONS
260 283
261 - could be faster, especially when the core would introduce special 284 - you must make very sure that no coro is still active on global destruction.
262 support for coroutines (like it does for threads). 285 very bad things might happen otherwise (usually segfaults).
263 - there is still a memleak on coroutine termination that I could not
264 identify. Could be as small as a single SV.
265 - this module is not well-tested.
266 - if variables or arguments "disappear" (become undef) or become
267 corrupted please contact the author so he cen iron out the
268 remaining bugs.
269 - this module is not thread-safe. You must only ever use this module from 286 - this module is not thread-safe. You must only ever use this module from
270 the same thread (this requirement might be loosened in the future to 287 the same thread (this requirement might be loosened in the future to
271 allow per-thread schedulers, but Coro::State does not yet allow this). 288 allow per-thread schedulers, but Coro::State does not yet allow this).
272 289
273=head1 SEE ALSO 290=head1 SEE ALSO

Diff Legend

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