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

Comparing Coro/Coro.pm (file contents):
Revision 1.27 by root, Sat Jul 28 01:41: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.13; 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;
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 172
181sub 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 {
182 $current->ready; 182 $current->cancel;
183 &schedule; 183 &schedule;
184}
185
186=item terminate
187
188Terminates the current process.
189
190Future versions of this function will allow result arguments.
191
192=cut
193
194sub terminate {
195 push @destroy, $current;
196 $manager->ready;
197 &schedule;
198 # NORETURN 184 die; # NORETURN
199} 185}
200 186
201=back 187=back
202 188
203# dynamic methods 189# dynamic methods
… …
234 220
235Put the current process into the ready queue. 221Put the current process into the ready queue.
236 222
237=cut 223=cut
238 224
239sub ready { 225=item $process->cancel
226
227Like C<terminate>, but terminates the specified process instead.
228
229=cut
230
231sub cancel {
240 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];
241} 275}
242 276
243=back 277=back
244 278
245=cut 279=cut
246 280
2471; 2811;
248 282
249=head1 BUGS/LIMITATIONS 283=head1 BUGS/LIMITATIONS
250 284
251 - 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.
252 support for coroutines (like it does for threads). 286 very bad things might happen otherwise (usually segfaults).
253 - there is still a memleak on coroutine termination that I could not
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 287 - this module is not thread-safe. You must only ever use this module from
260 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
261 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).
262 290
263=head1 SEE ALSO 291=head1 SEE ALSO

Diff Legend

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