| … | |
… | |
| 50 | |
50 | |
| 51 | our $idle; # idle handler |
51 | our $idle; # idle handler |
| 52 | our $main; # main coroutine |
52 | our $main; # main coroutine |
| 53 | our $current; # current coroutine |
53 | our $current; # current coroutine |
| 54 | |
54 | |
| 55 | our $VERSION = '3.5'; |
55 | our $VERSION = '3.56'; |
| 56 | |
56 | |
| 57 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
57 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
| 58 | our %EXPORT_TAGS = ( |
58 | our %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 | ); |
| … | |
… | |
| 185 | |
185 | |
| 186 | Create a new asynchronous coroutine and return it's coroutine object |
186 | Create a new asynchronous coroutine and return it's coroutine object |
| 187 | (usually unused). When the sub returns the new coroutine is automatically |
187 | (usually unused). When the sub returns the new coroutine is automatically |
| 188 | terminated. |
188 | terminated. |
| 189 | |
189 | |
| 190 | Calling C<exit> in a coroutine will not work correctly, so do not do that. |
190 | Calling C<exit> in a coroutine will do the same as calling exit outside |
| 191 | |
191 | the coroutine. Likewise, when the coroutine dies, the program will exit, |
| 192 | When the coroutine dies, the program will exit, just as in the main |
192 | just as it would in the main program. |
| 193 | program. |
|
|
| 194 | |
193 | |
| 195 | # create a new coroutine that just prints its arguments |
194 | # create a new coroutine that just prints its arguments |
| 196 | async { |
195 | async { |
| 197 | print "@_\n"; |
196 | print "@_\n"; |
| 198 | } 1,2,3,4; |
197 | } 1,2,3,4; |
| … | |
… | |
| 242 | warn $@ if $@; |
241 | warn $@ if $@; |
| 243 | |
242 | |
| 244 | last if @pool >= $POOL_SIZE; |
243 | last if @pool >= $POOL_SIZE; |
| 245 | push @pool, $current; |
244 | push @pool, $current; |
| 246 | |
245 | |
|
|
246 | $current->save (Coro::State::SAVE_DEF); |
| 247 | $current->prio (0); |
247 | $current->prio (0); |
| 248 | schedule; |
248 | schedule; |
| 249 | } |
249 | } |
| 250 | } |
250 | } |
| 251 | |
251 | |
| … | |
… | |
| 325 | Create a new coroutine and return it. When the sub returns the coroutine |
325 | Create a new coroutine and return it. When the sub returns the coroutine |
| 326 | automatically terminates as if C<terminate> with the returned values were |
326 | automatically terminates as if C<terminate> with the returned values were |
| 327 | called. To make the coroutine run you must first put it into the ready queue |
327 | called. To make the coroutine run you must first put it into the ready queue |
| 328 | by calling the ready method. |
328 | by calling the ready method. |
| 329 | |
329 | |
| 330 | Calling C<exit> in a coroutine will not work correctly, so do not do that. |
330 | See C<async> for additional discussion. |
| 331 | |
331 | |
| 332 | =cut |
332 | =cut |
| 333 | |
333 | |
| 334 | sub _run_coro { |
334 | sub _run_coro { |
| 335 | terminate &{+shift}; |
335 | terminate &{+shift}; |
| … | |
… | |
| 465 | and C<schedule> would cause a deadlock unless there is an idle handler |
465 | and C<schedule> would cause a deadlock unless there is an idle handler |
| 466 | that wakes up some coroutines. |
466 | that wakes up some coroutines. |
| 467 | |
467 | |
| 468 | =item my $guard = Coro::guard { ... } |
468 | =item my $guard = Coro::guard { ... } |
| 469 | |
469 | |
| 470 | This creates and returns a guard object. Nothing happens until the objetc |
470 | This creates and returns a guard object. Nothing happens until the object |
| 471 | gets destroyed, in which case the codeblock given as argument will be |
471 | gets destroyed, in which case the codeblock given as argument will be |
| 472 | executed. This is useful to free locks or other resources in case of a |
472 | executed. This is useful to free locks or other resources in case of a |
| 473 | runtime error or when the coroutine gets canceled, as in both cases the |
473 | runtime error or when the coroutine gets canceled, as in both cases the |
| 474 | guard block will be executed. The guard object supports only one method, |
474 | guard block will be executed. The guard object supports only one method, |
| 475 | C<< ->cancel >>, which will keep the codeblock from being executed. |
475 | C<< ->cancel >>, which will keep the codeblock from being executed. |
