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

Comparing Coro/Coro.pm (file contents):
Revision 1.105 by root, Fri Jan 5 16:55:01 2007 UTC vs.
Revision 1.108 by root, Fri Jan 5 20:00:49 2007 UTC

… …
210Similar to C<async>, but uses a coroutine pool, so you should not call 210Similar to C<async>, but uses a coroutine pool, so you should not call
211terminate or join (although you are allowed to), and you get a coroutine 211terminate or join (although you are allowed to), and you get a coroutine
212that might have executed other code already (which can be good or bad :). 212that might have executed other code already (which can be good or bad :).
213 213
214Also, the block is executed in an C<eval> context and a warning will be 214Also, the block is executed in an C<eval> context and a warning will be
215issued in case of an exception instead of terminating the program, as C<async> does. 215issued in case of an exception instead of terminating the program, as
216C<async> does. As the coroutine is being reused, stuff like C<on_destroy>
217will not work in the expected way, unless you call terminate or cancel,
218which somehow defeats the purpose of pooling.
216 219
217The priority will be reset to C<0> after each job, otherwise the coroutine 220The priority will be reset to C<0> after each job, otherwise the coroutine
218will be re-used "as-is". 221will be re-used "as-is".
219 222
220The pool size is limited to 8 idle coroutines (this can be adjusted by 223The pool size is limited to 8 idle coroutines (this can be adjusted by
… …
242 last if @pool >= $POOL_SIZE; 245 last if @pool >= $POOL_SIZE;
243 push @pool, $current; 246 push @pool, $current;
244 247
245 $current->prio (0); 248 $current->prio (0);
246 schedule; 249 schedule;
247 } 250 }
248} 251}
249 252
250sub async_pool(&@) { 253sub async_pool(&@) {
251 # this is also inlined into the unlock_scheduler 254 # this is also inlined into the unlock_scheduler
252 my $coro = (pop @pool or new Coro \&pool_handler); 255 my $coro = (pop @pool or new Coro \&pool_handler);
253 256
… …
287 290
288"Cede" to other coroutines. This function puts the current coroutine into the 291"Cede" to other coroutines. This function puts the current coroutine into the
289ready queue and calls C<schedule>, which has the effect of giving up the 292ready queue and calls C<schedule>, which has the effect of giving up the
290current "timeslice" to other coroutines of the same or higher priority. 293current "timeslice" to other coroutines of the same or higher priority.
291 294
295Returns true if at least one coroutine switch has happened.
296
292=item Coro::cede_notself 297=item Coro::cede_notself
293 298
294Works like cede, but is not exported by default and will cede to any 299Works like cede, but is not exported by default and will cede to any
295coroutine, regardless of priority, once. 300coroutine, regardless of priority, once.
301
302Returns true if at least one coroutine switch has happened.
296 303
297=item terminate [arg...] 304=item terminate [arg...]
298 305
299Terminates the current coroutine with the given status values (see L<cancel>). 306Terminates the current coroutine with the given status values (see L<cancel>).
300 307

Diff Legend

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