| … | |
… | |
| 857 | otherwise you might suffer from crashes or worse. The only event |
857 | otherwise you might suffer from crashes or worse. The only event |
| 858 | library currently known that is safe to use without "unblock_sub" is |
858 | library currently known that is safe to use without "unblock_sub" is |
| 859 | EV (but you might still run into deadlocks if all event loops are |
859 | EV (but you might still run into deadlocks if all event loops are |
| 860 | blocked). |
860 | blocked). |
| 861 | |
861 | |
| 862 | Coro will try to catch you when you block in the event loop |
862 | Coro will try to catch you when you block in the event loop ("FATAL: |
| 863 | ("FATAL:$Coro::idle blocked itself"), but this is just best effort |
863 | $Coro::idle blocked itself"), but this is just best effort and only |
| 864 | and only works when you do not run your own event loop. |
864 | works when you do not run your own event loop. |
| 865 | |
865 | |
| 866 | This function allows your callbacks to block by executing them in |
866 | This function allows your callbacks to block by executing them in |
| 867 | another coro where it is safe to block. One example where blocking |
867 | another coro where it is safe to block. One example where blocking |
| 868 | is handy is when you use the Coro::AIO functions to save results to |
868 | is handy is when you use the Coro::AIO functions to save results to |
| 869 | disk, for example. |
869 | disk, for example. |
