… | |
… | |
81 | |
81 | |
82 | our $idle; # idle handler |
82 | our $idle; # idle handler |
83 | our $main; # main coro |
83 | our $main; # main coro |
84 | our $current; # current coro |
84 | our $current; # current coro |
85 | |
85 | |
86 | our $VERSION = 5.2; |
86 | our $VERSION = 5.21; |
87 | |
87 | |
88 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait); |
88 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait); |
89 | our %EXPORT_TAGS = ( |
89 | our %EXPORT_TAGS = ( |
90 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
90 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
91 | ); |
91 | ); |
… | |
… | |
665 | venerable L<Event|Event> module) are not thread-safe (a weaker form |
665 | venerable L<Event|Event> module) are not thread-safe (a weaker form |
666 | of reentrancy). This means you must not block within event callbacks, |
666 | of reentrancy). This means you must not block within event callbacks, |
667 | otherwise you might suffer from crashes or worse. The only event library |
667 | otherwise you might suffer from crashes or worse. The only event library |
668 | currently known that is safe to use without C<unblock_sub> is L<EV>. |
668 | currently known that is safe to use without C<unblock_sub> is L<EV>. |
669 | |
669 | |
|
|
670 | Coro will try to catch you when you block in the event loop |
|
|
671 | ("FATAL:$Coro::IDLE blocked itself"), but this is just best effort and |
|
|
672 | only works when you do not run your own event loop. |
|
|
673 | |
670 | This function allows your callbacks to block by executing them in another |
674 | This function allows your callbacks to block by executing them in another |
671 | coro where it is safe to block. One example where blocking is handy |
675 | coro where it is safe to block. One example where blocking is handy |
672 | is when you use the L<Coro::AIO|Coro::AIO> functions to save results to |
676 | is when you use the L<Coro::AIO|Coro::AIO> functions to save results to |
673 | disk, for example. |
677 | disk, for example. |
674 | |
678 | |
… | |
… | |
830 | the windows process emulation enabled under unix roughly halves perl |
834 | the windows process emulation enabled under unix roughly halves perl |
831 | performance, even when not used. |
835 | performance, even when not used. |
832 | |
836 | |
833 | =item coro switching is not signal safe |
837 | =item coro switching is not signal safe |
834 | |
838 | |
835 | You must not switch to another coro from within a signal handler |
839 | You must not switch to another coro from within a signal handler (only |
836 | (only relevant with %SIG - most event libraries provide safe signals). |
840 | relevant with %SIG - most event libraries provide safe signals), I<unless> |
|
|
841 | you are sure you are not interrupting a Coro function. |
837 | |
842 | |
838 | That means you I<MUST NOT> call any function that might "block" the |
843 | That means you I<MUST NOT> call any function that might "block" the |
839 | current coro - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or |
844 | current coro - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or |
840 | anything that calls those. Everything else, including calling C<ready>, |
845 | anything that calls those. Everything else, including calling C<ready>, |
841 | works. |
846 | works. |