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

Comparing Coro/Coro.pm (file contents):
Revision 1.107 by root, Fri Jan 5 18:25:51 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

Diff Legend

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