| … | |
… | |
| 67 | |
67 | |
| 68 | our $idle; # idle handler |
68 | our $idle; # idle handler |
| 69 | our $main; # main coroutine |
69 | our $main; # main coroutine |
| 70 | our $current; # current coroutine |
70 | our $current; # current coroutine |
| 71 | |
71 | |
| 72 | our $VERSION = 4.749; |
72 | our $VERSION = 4.8; |
| 73 | |
73 | |
| 74 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
74 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
| 75 | our %EXPORT_TAGS = ( |
75 | our %EXPORT_TAGS = ( |
| 76 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
76 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
| 77 | ); |
77 | ); |
| … | |
… | |
| 221 | terminate or join on it (although you are allowed to), and you get a |
221 | terminate or join on it (although you are allowed to), and you get a |
| 222 | coroutine that might have executed other code already (which can be good |
222 | coroutine that might have executed other code already (which can be good |
| 223 | or bad :). |
223 | or bad :). |
| 224 | |
224 | |
| 225 | On the plus side, this function is faster than creating (and destroying) |
225 | On the plus side, this function is faster than creating (and destroying) |
| 226 | a completely new coroutine, so if you need a lot of generic coroutines in |
226 | a completly new coroutine, so if you need a lot of generic coroutines in |
| 227 | quick successsion, use C<async_pool>, not C<async>. |
227 | quick successsion, use C<async_pool>, not C<async>. |
| 228 | |
228 | |
| 229 | The code block is executed in an C<eval> context and a warning will be |
229 | The code block is executed in an C<eval> context and a warning will be |
| 230 | issued in case of an exception instead of terminating the program, as |
230 | issued in case of an exception instead of terminating the program, as |
| 231 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
231 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
