ViewVC Help
View File | Revision Log | Show Annotations | Download File
/cvs/Coro/Coro.pm
(Generate patch)

Comparing Coro/Coro.pm (file contents):
Revision 1.273 by root, Fri Dec 11 18:32:23 2009 UTC vs.
Revision 1.274 by root, Sat Dec 12 01:30:26 2009 UTC

… …
665venerable L<Event|Event> module) are not thread-safe (a weaker form 665venerable L<Event|Event> module) are not thread-safe (a weaker form
666of reentrancy). This means you must not block within event callbacks, 666of reentrancy). This means you must not block within event callbacks,
667otherwise you might suffer from crashes or worse. The only event library 667otherwise you might suffer from crashes or worse. The only event library
668currently known that is safe to use without C<unblock_sub> is L<EV>. 668currently known that is safe to use without C<unblock_sub> is L<EV>.
669 669
670Coro 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
672only works when you do not run your own event loop.
673
670This function allows your callbacks to block by executing them in another 674This function allows your callbacks to block by executing them in another
671coro where it is safe to block. One example where blocking is handy 675coro where it is safe to block. One example where blocking is handy
672is when you use the L<Coro::AIO|Coro::AIO> functions to save results to 676is when you use the L<Coro::AIO|Coro::AIO> functions to save results to
673disk, for example. 677disk, for example.
674 678

Diff Legend

– Removed lines
+ Added lines
< Changed lines
> Changed lines