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

Comparing Coro/Coro.pm (file contents):
Revision 1.269 by root, Thu Oct 1 23:25:03 2009 UTC vs.
Revision 1.270 by root, Thu Oct 1 23:50:23 2009 UTC

… …
124 124
125This variable is mainly useful to integrate Coro into event loops. It is 125This variable is mainly useful to integrate Coro into event loops. It is
126usually better to rely on L<Coro::AnyEvent> or L<Coro::EV>, as this is 126usually better to rely on L<Coro::AnyEvent> or L<Coro::EV>, as this is
127pretty low-level functionality. 127pretty low-level functionality.
128 128
129This variable stores either a Coro object or a callback. 129This variable stores a Coro object that is put into the ready queue when
130there are no other ready threads (without invoking any ready hooks).
130 131
131If it is a callback, the it is called whenever the scheduler finds no 132The default implementation dies with "FATAL: deadlock detected.", followed
132ready coros to run. The default implementation prints "FATAL: 133by a thread listing, because the program has no other way to continue.
133deadlock detected" and exits, because the program has no other way to
134continue.
135
136If it is a coro object, then this object will be readied (without
137invoking any ready hooks, however) when the scheduler finds no other ready
138coros to run.
139 134
140This hook is overwritten by modules such as C<Coro::EV> and 135This hook is overwritten by modules such as C<Coro::EV> and
141C<Coro::AnyEvent> to wait on an external event that hopefully wake up a 136C<Coro::AnyEvent> to wait on an external event that hopefully wake up a
142coro so the scheduler can run it. 137coro so the scheduler can run it.
143 138
144Note that the callback I<must not>, under any circumstances, block
145the current coro. Normally, this is achieved by having an "idle
146coro" that calls the event loop and then blocks again, and then
147readying that coro in the idle handler, or by simply placing the idle
148coro in this variable.
149
150See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this 139See L<Coro::EV> or L<Coro::AnyEvent> for examples of using this technique.
151technique.
152 140
153Please note that if your callback recursively invokes perl (e.g. for event
154handlers), then it must be prepared to be called recursively itself.
155
156=cut 141=cut
157 142
158$idle = sub { 143$idle = new Coro sub {
159 Carp::confess ("FATAL: deadlock detected"); 144 require Coro::Debug;
145 die "FATAL: deadlock detected.\n"
146 . Coro::Debug::ps_listing ();
160}; 147};
161 148
162# this coro is necessary because a coro 149# this coro is necessary because a coro
163# cannot destroy itself. 150# cannot destroy itself.
164our @destroy; 151our @destroy;
… …
272=item schedule 259=item schedule
273 260
274Calls the scheduler. The scheduler will find the next coro that is 261Calls the scheduler. The scheduler will find the next coro that is
275to be run from the ready queue and switches to it. The next coro 262to be run from the ready queue and switches to it. The next coro
276to be run is simply the one with the highest priority that is longest 263to be run is simply the one with the highest priority that is longest
277in its ready queue. If there is no coro ready, it will clal the 264in its ready queue. If there is no coro ready, it will call the
278C<$Coro::idle> hook. 265C<$Coro::idle> hook.
279 266
280Please note that the current coro will I<not> be put into the ready 267Please note that the current coro will I<not> be put into the ready
281queue, so calling this function usually means you will never be called 268queue, so calling this function usually means you will never be called
282again unless something else (e.g. an event handler) calls C<< ->ready >>, 269again unless something else (e.g. an event handler) calls C<< ->ready >>,

Diff Legend

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