… | |
… | |
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 | |