… | |
… | |
80 | |
80 | |
81 | our $idle; # idle handler |
81 | our $idle; # idle handler |
82 | our $main; # main coro |
82 | our $main; # main coro |
83 | our $current; # current coro |
83 | our $current; # current coro |
84 | |
84 | |
85 | our $VERSION = 5.132; |
85 | our $VERSION = 5.16; |
86 | |
86 | |
87 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
87 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
88 | our %EXPORT_TAGS = ( |
88 | our %EXPORT_TAGS = ( |
89 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
89 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
90 | ); |
90 | ); |
… | |
… | |
373 | }; |
373 | }; |
374 | |
374 | |
375 | This can be used to localise about any resource (locale, uid, current |
375 | This can be used to localise about any resource (locale, uid, current |
376 | working directory etc.) to a block, despite the existance of other |
376 | working directory etc.) to a block, despite the existance of other |
377 | coros. |
377 | coros. |
|
|
378 | |
|
|
379 | Another interesting example implements time-sliced multitasking using |
|
|
380 | interval timers (this could obviously be optimised, but does the job): |
|
|
381 | |
|
|
382 | # "timeslice" the given block |
|
|
383 | sub timeslice(&) { |
|
|
384 | use Time::HiRes (); |
|
|
385 | |
|
|
386 | Coro::on_enter { |
|
|
387 | # on entering the thread, we set an VTALRM handler to cede |
|
|
388 | $SIG{VTALRM} = sub { cede }; |
|
|
389 | # and then start the interval timer |
|
|
390 | Time::HiRes::setitimer &Time::HiRes::ITIMER_VIRTUAL, 0.01, 0.01; |
|
|
391 | }; |
|
|
392 | Coro::on_leave { |
|
|
393 | # on leaving the thread, we stop the interval timer again |
|
|
394 | Time::HiRes::setitimer &Time::HiRes::ITIMER_VIRTUAL, 0, 0; |
|
|
395 | }; |
|
|
396 | |
|
|
397 | &{+shift}; |
|
|
398 | } |
|
|
399 | |
|
|
400 | # use like this: |
|
|
401 | timeslice { |
|
|
402 | # The following is an endless loop that would normally |
|
|
403 | # monopolise the process. Since it runs in a timesliced |
|
|
404 | # environment, it will regularly cede to other threads. |
|
|
405 | while () { } |
|
|
406 | }; |
|
|
407 | |
378 | |
408 | |
379 | =item killall |
409 | =item killall |
380 | |
410 | |
381 | Kills/terminates/cancels all coros except the currently running one. |
411 | Kills/terminates/cancels all coros except the currently running one. |
382 | |
412 | |
… | |
… | |
721 | Wait for the specified rouse callback (or the last one that was created in |
751 | Wait for the specified rouse callback (or the last one that was created in |
722 | this coro). |
752 | this coro). |
723 | |
753 | |
724 | As soon as the callback is invoked (or when the callback was invoked |
754 | As soon as the callback is invoked (or when the callback was invoked |
725 | before C<rouse_wait>), it will return the arguments originally passed to |
755 | before C<rouse_wait>), it will return the arguments originally passed to |
726 | the rouse callback. |
756 | the rouse callback. In scalar context, that means you get the I<last> |
|
|
757 | argument, just as if C<rouse_wait> had a C<return ($a1, $a2, $a3...)> |
|
|
758 | statement at the end. |
727 | |
759 | |
728 | See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example. |
760 | See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example. |
729 | |
761 | |
730 | =back |
762 | =back |
731 | |
763 | |