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

Comparing cvsroot/Coro/Coro.pm (file contents):
Revision 1.271 by root, Fri Oct 2 19:55:59 2009 UTC vs.
Revision 1.275 by root, Wed Mar 31 17:41:07 2010 UTC

… …
81 81
82our $idle; # idle handler 82our $idle; # idle handler
83our $main; # main coro 83our $main; # main coro
84our $current; # current coro 84our $current; # current coro
85 85
86our $VERSION = 5.2; 86our $VERSION = 5.21;
87 87
88our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait); 88our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait);
89our %EXPORT_TAGS = ( 89our %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);
… …
138 138
139See L<Coro::EV> or L<Coro::AnyEvent> for examples of using this technique. 139See L<Coro::EV> or L<Coro::AnyEvent> for examples of using this technique.
140 140
141=cut 141=cut
142 142
143# ||= because other modules could have provided their own by now
143$idle = new Coro sub { 144$idle ||= new Coro sub {
144 require Coro::Debug; 145 require Coro::Debug;
145 die "FATAL: deadlock detected.\n" 146 die "FATAL: deadlock detected.\n"
146 . Coro::Debug::ps_listing (); 147 . Coro::Debug::ps_listing ();
147}; 148};
148 149
… …
665venerable L<Event|Event> module) are not thread-safe (a weaker form 666venerable L<Event|Event> module) are not thread-safe (a weaker form
666of reentrancy). This means you must not block within event callbacks, 667of reentrancy). This means you must not block within event callbacks,
667otherwise you might suffer from crashes or worse. The only event library 668otherwise 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>. 669currently known that is safe to use without C<unblock_sub> is L<EV>.
669 670
671Coro will try to catch you when you block in the event loop
672("FATAL:$Coro::IDLE blocked itself"), but this is just best effort and
673only works when you do not run your own event loop.
674
670This function allows your callbacks to block by executing them in another 675This function allows your callbacks to block by executing them in another
671coro where it is safe to block. One example where blocking is handy 676coro 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 677is when you use the L<Coro::AIO|Coro::AIO> functions to save results to
673disk, for example. 678disk, for example.
674 679
… …
830the windows process emulation enabled under unix roughly halves perl 835the windows process emulation enabled under unix roughly halves perl
831performance, even when not used. 836performance, even when not used.
832 837
833=item coro switching is not signal safe 838=item coro switching is not signal safe
834 839
835You must not switch to another coro from within a signal handler 840You must not switch to another coro from within a signal handler (only
836(only relevant with %SIG - most event libraries provide safe signals). 841relevant with %SIG - most event libraries provide safe signals), I<unless>
842you are sure you are not interrupting a Coro function.
837 843
838That means you I<MUST NOT> call any function that might "block" the 844That means you I<MUST NOT> call any function that might "block" the
839current coro - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or 845current coro - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or
840anything that calls those. Everything else, including calling C<ready>, 846anything that calls those. Everything else, including calling C<ready>,
841works. 847works.

Diff Legend

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