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

Comparing Coro/Coro.pm (file contents):
Revision 1.106 by root, Fri Jan 5 17:44:17 2007 UTC vs.
Revision 1.119 by root, Wed Mar 28 14:24:17 2007 UTC

… …
50 50
51our $idle; # idle handler 51our $idle; # idle handler
52our $main; # main coroutine 52our $main; # main coroutine
53our $current; # current coroutine 53our $current; # current coroutine
54 54
55our $VERSION = '3.3'; 55our $VERSION = '3.55';
56 56
57our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); 57our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
58our %EXPORT_TAGS = ( 58our %EXPORT_TAGS = (
59 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], 59 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
60); 60);
… …
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
… …
230our $POOL_SIZE = 8; 233our $POOL_SIZE = 8;
231our @pool; 234our @pool;
232 235
233sub pool_handler { 236sub pool_handler {
234 while () { 237 while () {
235 my ($cb, @arg) = @{ delete $current->{_invoke} };
236
237 eval { 238 eval {
239 my ($cb, @arg) = @{ delete $current->{_invoke} or return };
238 $cb->(@arg); 240 $cb->(@arg);
239 }; 241 };
240 warn $@ if $@; 242 warn $@ if $@;
241 243
242 last if @pool >= $POOL_SIZE; 244 last if @pool >= $POOL_SIZE;
243 push @pool, $current; 245 push @pool, $current;
244 246
247 $current->save (Coro::State::SAVE_DEF);
245 $current->prio (0); 248 $current->prio (0);
246 schedule; 249 schedule;
247 } 250 }
248} 251}
249 252
… …
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
… …
459and C<schedule> would cause a deadlock unless there is an idle handler 466and C<schedule> would cause a deadlock unless there is an idle handler
460that wakes up some coroutines. 467that wakes up some coroutines.
461 468
462=item my $guard = Coro::guard { ... } 469=item my $guard = Coro::guard { ... }
463 470
464This creates and returns a guard object. Nothing happens until the objetc 471This creates and returns a guard object. Nothing happens until the object
465gets destroyed, in which case the codeblock given as argument will be 472gets destroyed, in which case the codeblock given as argument will be
466executed. This is useful to free locks or other resources in case of a 473executed. This is useful to free locks or other resources in case of a
467runtime error or when the coroutine gets canceled, as in both cases the 474runtime error or when the coroutine gets canceled, as in both cases the
468guard block will be executed. The guard object supports only one method, 475guard block will be executed. The guard object supports only one method,
469C<< ->cancel >>, which will keep the codeblock from being executed. 476C<< ->cancel >>, which will keep the codeblock from being executed.

Diff Legend

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