… | |
… | |
25 | $locked = 1; |
25 | $locked = 1; |
26 | $lock->up; |
26 | $lock->up; |
27 | |
27 | |
28 | =head1 DESCRIPTION |
28 | =head1 DESCRIPTION |
29 | |
29 | |
30 | This module collection manages coroutines. Coroutines are similar |
30 | This module collection manages coroutines. Coroutines are similar to |
31 | to threads but don't run in parallel at the same time even on SMP |
31 | threads but don't (in general) run in parallel at the same time even |
32 | machines. The specific flavor of coroutine used in this module also |
32 | on SMP machines. The specific flavor of coroutine used in this module |
33 | guarantees you that it will not switch between coroutines unless |
33 | also guarantees you that it will not switch between coroutines unless |
34 | necessary, at easily-identified points in your program, so locking and |
34 | necessary, at easily-identified points in your program, so locking and |
35 | parallel access are rarely an issue, making coroutine programming much |
35 | parallel access are rarely an issue, making coroutine programming much |
36 | safer than threads programming. |
36 | safer and easier than threads programming. |
37 | |
37 | |
38 | (Perl, however, does not natively support real threads but instead does a |
38 | Unlike a normal perl program, however, coroutines allow you to have |
39 | very slow and memory-intensive emulation of processes using threads. This |
39 | multiple running interpreters that share data, which is especially useful |
40 | is a performance win on Windows machines, and a loss everywhere else). |
40 | to code pseudo-parallel processes and for event-based programming, such as |
|
|
41 | multiple HTTP-GET requests running concurrently. See L<Coro::AnyEvent> to |
|
|
42 | learn more. |
|
|
43 | |
|
|
44 | Coroutines are also useful because Perl has no support for threads (the so |
|
|
45 | called "threads" that perl offers are nothing more than the (bad) process |
|
|
46 | emulation coming from the Windows platform: On standard operating systems |
|
|
47 | they serve no purpose whatsoever, except by making your programs slow and |
|
|
48 | making them use a lot of memory. Best disable them when building perl, or |
|
|
49 | aks your software vendor/distributor to do it for you). |
41 | |
50 | |
42 | In this module, coroutines are defined as "callchain + lexical variables + |
51 | In this module, coroutines are defined as "callchain + lexical variables + |
43 | @_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain, |
52 | @_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain, |
44 | its own set of lexicals and its own set of perls most important global |
53 | its own set of lexicals and its own set of perls most important global |
45 | variables (see L<Coro::State> for more configuration). |
54 | variables (see L<Coro::State> for more configuration). |
… | |
… | |
57 | |
66 | |
58 | our $idle; # idle handler |
67 | our $idle; # idle handler |
59 | our $main; # main coroutine |
68 | our $main; # main coroutine |
60 | our $current; # current coroutine |
69 | our $current; # current coroutine |
61 | |
70 | |
62 | our $VERSION = 4.6; |
71 | our $VERSION = 4.74; |
63 | |
72 | |
64 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
73 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
65 | our %EXPORT_TAGS = ( |
74 | our %EXPORT_TAGS = ( |
66 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
75 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
67 | ); |
76 | ); |
68 | our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready)); |
77 | our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready)); |
69 | |
78 | |
70 | =over 4 |
79 | =over 4 |
71 | |
80 | |
72 | =item $main |
81 | =item $Coro::main |
73 | |
82 | |
74 | This coroutine represents the main program. |
83 | This variable stores the coroutine object that represents the main |
|
|
84 | program. While you cna C<ready> it and do most other things you can do to |
|
|
85 | coroutines, it is mainly useful to compare again C<$Coro::current>, to see |
|
|
86 | wether you are running in the main program or not. |
75 | |
87 | |
76 | =cut |
88 | =cut |
77 | |
89 | |
78 | $main = new Coro; |
90 | $main = new Coro; |
79 | |
91 | |
80 | =item $current (or as function: current) |
92 | =item $Coro::current |
81 | |
93 | |
82 | The current coroutine (the last coroutine switched to). The initial value |
94 | The coroutine object representing the current coroutine (the last |
|
|
95 | coroutine that the Coro scheduler switched to). The initial value is |
83 | is C<$main> (of course). |
96 | C<$main> (of course). |
84 | |
97 | |
85 | This variable is B<strictly> I<read-only>. It is provided for performance |
98 | This variable is B<strictly> I<read-only>. You can take copies of the |
86 | reasons. If performance is not essential you are encouraged to use the |
99 | value stored in it and use it as any other coroutine object, but you must |
87 | C<Coro::current> function instead. |
100 | not otherwise modify the variable itself. |
88 | |
101 | |
89 | =cut |
102 | =cut |
90 | |
103 | |
91 | $main->{desc} = "[main::]"; |
104 | $main->{desc} = "[main::]"; |
92 | |
105 | |
… | |
… | |
94 | $main->{_specific} = $current->{_specific} |
107 | $main->{_specific} = $current->{_specific} |
95 | if $current; |
108 | if $current; |
96 | |
109 | |
97 | _set_current $main; |
110 | _set_current $main; |
98 | |
111 | |
99 | sub current() { $current } |
112 | sub current() { $current } # [DEPRECATED] |
100 | |
113 | |
101 | =item $idle |
114 | =item $Coro::idle |
102 | |
115 | |
103 | A callback that is called whenever the scheduler finds no ready coroutines |
116 | This variable is mainly useful to integrate Coro into event loops. It is |
104 | to run. The default implementation prints "FATAL: deadlock detected" and |
117 | usually better to rely on L<Coro::AnyEvent> or LC<Coro::EV>, as this is |
105 | exits, because the program has no other way to continue. |
118 | pretty low-level functionality. |
|
|
119 | |
|
|
120 | This variable stores a callback that is called whenever the scheduler |
|
|
121 | finds no ready coroutines to run. The default implementation prints |
|
|
122 | "FATAL: deadlock detected" and exits, because the program has no other way |
|
|
123 | to continue. |
106 | |
124 | |
107 | This hook is overwritten by modules such as C<Coro::Timer> and |
125 | This hook is overwritten by modules such as C<Coro::Timer> and |
108 | C<Coro::Event> to wait on an external event that hopefully wake up a |
126 | C<Coro::AnyEvent> to wait on an external event that hopefully wake up a |
109 | coroutine so the scheduler can run it. |
127 | coroutine so the scheduler can run it. |
|
|
128 | |
|
|
129 | Note that the callback I<must not>, under any circumstances, block |
|
|
130 | the current coroutine. Normally, this is achieved by having an "idle |
|
|
131 | coroutine" that calls the event loop and then blocks again, and then |
|
|
132 | readying that coroutine in the idle handler. |
|
|
133 | |
|
|
134 | See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this |
|
|
135 | technique. |
110 | |
136 | |
111 | Please note that if your callback recursively invokes perl (e.g. for event |
137 | Please note that if your callback recursively invokes perl (e.g. for event |
112 | handlers), then it must be prepared to be called recursively itself. |
138 | handlers), then it must be prepared to be called recursively itself. |
113 | |
139 | |
114 | =cut |
140 | =cut |
… | |
… | |
146 | $manager->desc ("[coro manager]"); |
172 | $manager->desc ("[coro manager]"); |
147 | $manager->prio (PRIO_MAX); |
173 | $manager->prio (PRIO_MAX); |
148 | |
174 | |
149 | =back |
175 | =back |
150 | |
176 | |
151 | =head2 STATIC METHODS |
177 | =head2 SIMPLE COROUTINE CREATION |
152 | |
|
|
153 | Static methods are actually functions that operate on the current coroutine only. |
|
|
154 | |
178 | |
155 | =over 4 |
179 | =over 4 |
156 | |
180 | |
157 | =item async { ... } [@args...] |
181 | =item async { ... } [@args...] |
158 | |
182 | |
159 | Create a new asynchronous coroutine and return it's coroutine object |
183 | Create a new coroutine and return it's coroutine object (usually |
160 | (usually unused). When the sub returns the new coroutine is automatically |
184 | unused). The coroutine will be put into the ready queue, so |
|
|
185 | it will start running automatically on the next scheduler run. |
|
|
186 | |
|
|
187 | The first argument is a codeblock/closure that should be executed in the |
|
|
188 | coroutine. When it returns argument returns the coroutine is automatically |
161 | terminated. |
189 | terminated. |
162 | |
190 | |
|
|
191 | The remaining arguments are passed as arguments to the closure. |
|
|
192 | |
163 | See the C<Coro::State::new> constructor for info about the coroutine |
193 | See the C<Coro::State::new> constructor for info about the coroutine |
164 | environment in which coroutines run. |
194 | environment in which coroutines are executed. |
165 | |
195 | |
166 | Calling C<exit> in a coroutine will do the same as calling exit outside |
196 | Calling C<exit> in a coroutine will do the same as calling exit outside |
167 | the coroutine. Likewise, when the coroutine dies, the program will exit, |
197 | the coroutine. Likewise, when the coroutine dies, the program will exit, |
168 | just as it would in the main program. |
198 | just as it would in the main program. |
169 | |
199 | |
|
|
200 | If you do not want that, you can provide a default C<die> handler, or |
|
|
201 | simply avoid dieing (by use of C<eval>). |
|
|
202 | |
170 | # create a new coroutine that just prints its arguments |
203 | Example: Create a new coroutine that just prints its arguments. |
|
|
204 | |
171 | async { |
205 | async { |
172 | print "@_\n"; |
206 | print "@_\n"; |
173 | } 1,2,3,4; |
207 | } 1,2,3,4; |
174 | |
208 | |
175 | =cut |
209 | =cut |
… | |
… | |
181 | } |
215 | } |
182 | |
216 | |
183 | =item async_pool { ... } [@args...] |
217 | =item async_pool { ... } [@args...] |
184 | |
218 | |
185 | Similar to C<async>, but uses a coroutine pool, so you should not call |
219 | Similar to C<async>, but uses a coroutine pool, so you should not call |
186 | terminate or join (although you are allowed to), and you get a coroutine |
220 | terminate or join on it (although you are allowed to), and you get a |
187 | that might have executed other code already (which can be good or bad :). |
221 | coroutine that might have executed other code already (which can be good |
|
|
222 | or bad :). |
188 | |
223 | |
|
|
224 | On the plus side, this function is faster than creating (and destroying) |
|
|
225 | a completely new coroutine, so if you need a lot of generic coroutines in |
|
|
226 | quick successsion, use C<async_pool>, not C<async>. |
|
|
227 | |
189 | Also, the block is executed in an C<eval> context and a warning will be |
228 | The code block is executed in an C<eval> context and a warning will be |
190 | issued in case of an exception instead of terminating the program, as |
229 | issued in case of an exception instead of terminating the program, as |
191 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
230 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
192 | will not work in the expected way, unless you call terminate or cancel, |
231 | will not work in the expected way, unless you call terminate or cancel, |
193 | which somehow defeats the purpose of pooling. |
232 | which somehow defeats the purpose of pooling (but is fine in the |
|
|
233 | exceptional case). |
194 | |
234 | |
195 | The priority will be reset to C<0> after each job, tracing will be |
235 | The priority will be reset to C<0> after each run, tracing will be |
196 | disabled, the description will be reset and the default output filehandle |
236 | disabled, the description will be reset and the default output filehandle |
197 | gets restored, so you can change alkl these. Otherwise the coroutine will |
237 | gets restored, so you can change all these. Otherwise the coroutine will |
198 | be re-used "as-is": most notably if you change other per-coroutine global |
238 | be re-used "as-is": most notably if you change other per-coroutine global |
199 | stuff such as C<$/> you need to revert that change, which is most simply |
239 | stuff such as C<$/> you I<must needs> to revert that change, which is most |
200 | done by using local as in C< local $/ >. |
240 | simply done by using local as in: C< local $/ >. |
201 | |
241 | |
202 | The pool size is limited to 8 idle coroutines (this can be adjusted by |
242 | The pool size is limited to C<8> idle coroutines (this can be adjusted by |
203 | changing $Coro::POOL_SIZE), and there can be as many non-idle coros as |
243 | changing $Coro::POOL_SIZE), and there can be as many non-idle coros as |
204 | required. |
244 | required. |
205 | |
245 | |
206 | If you are concerned about pooled coroutines growing a lot because a |
246 | If you are concerned about pooled coroutines growing a lot because a |
207 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
247 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
208 | { terminate }> once per second or so to slowly replenish the pool. In |
248 | { terminate }> once per second or so to slowly replenish the pool. In |
209 | addition to that, when the stacks used by a handler grows larger than 16kb |
249 | addition to that, when the stacks used by a handler grows larger than 16kb |
210 | (adjustable with $Coro::POOL_RSS) it will also exit. |
250 | (adjustable via $Coro::POOL_RSS) it will also be destroyed. |
211 | |
251 | |
212 | =cut |
252 | =cut |
213 | |
253 | |
214 | our $POOL_SIZE = 8; |
254 | our $POOL_SIZE = 8; |
215 | our $POOL_RSS = 16 * 1024; |
255 | our $POOL_RSS = 16 * 1024; |
… | |
… | |
241 | $coro->ready; |
281 | $coro->ready; |
242 | |
282 | |
243 | $coro |
283 | $coro |
244 | } |
284 | } |
245 | |
285 | |
|
|
286 | =back |
|
|
287 | |
|
|
288 | =head2 STATIC METHODS |
|
|
289 | |
|
|
290 | Static methods are actually functions that operate on the current coroutine. |
|
|
291 | |
|
|
292 | =over 4 |
|
|
293 | |
246 | =item schedule |
294 | =item schedule |
247 | |
295 | |
248 | Calls the scheduler. Please note that the current coroutine will not be put |
296 | Calls the scheduler. The scheduler will find the next coroutine that is |
|
|
297 | to be run from the ready queue and switches to it. The next coroutine |
|
|
298 | to be run is simply the one with the highest priority that is longest |
|
|
299 | in its ready queue. If there is no coroutine ready, it will clal the |
|
|
300 | C<$Coro::idle> hook. |
|
|
301 | |
|
|
302 | Please note that the current coroutine will I<not> be put into the ready |
249 | into the ready queue, so calling this function usually means you will |
303 | queue, so calling this function usually means you will never be called |
250 | never be called again unless something else (e.g. an event handler) calls |
304 | again unless something else (e.g. an event handler) calls C<< ->ready >>, |
251 | ready. |
305 | thus waking you up. |
|
|
306 | |
|
|
307 | This makes C<schedule> I<the> generic method to use to block the current |
|
|
308 | coroutine and wait for events: first you remember the current coroutine in |
|
|
309 | a variable, then arrange for some callback of yours to call C<< ->ready |
|
|
310 | >> on that once some event happens, and last you call C<schedule> to put |
|
|
311 | yourself to sleep. Note that a lot of things can wake your coroutine up, |
|
|
312 | so you need to check wether the event indeed happened, e.g. by storing the |
|
|
313 | status in a variable. |
252 | |
314 | |
253 | The canonical way to wait on external events is this: |
315 | The canonical way to wait on external events is this: |
254 | |
316 | |
255 | { |
317 | { |
256 | # remember current coroutine |
318 | # remember current coroutine |
… | |
… | |
269 | Coro::schedule while $current; |
331 | Coro::schedule while $current; |
270 | } |
332 | } |
271 | |
333 | |
272 | =item cede |
334 | =item cede |
273 | |
335 | |
274 | "Cede" to other coroutines. This function puts the current coroutine into the |
336 | "Cede" to other coroutines. This function puts the current coroutine into |
275 | ready queue and calls C<schedule>, which has the effect of giving up the |
337 | the ready queue and calls C<schedule>, which has the effect of giving |
276 | current "timeslice" to other coroutines of the same or higher priority. |
338 | up the current "timeslice" to other coroutines of the same or higher |
|
|
339 | priority. Once your coroutine gets its turn again it will automatically be |
|
|
340 | resumed. |
|
|
341 | |
|
|
342 | This function is often called C<yield> in other languages. |
277 | |
343 | |
278 | =item Coro::cede_notself |
344 | =item Coro::cede_notself |
279 | |
345 | |
280 | Works like cede, but is not exported by default and will cede to any |
346 | Works like cede, but is not exported by default and will cede to I<any> |
281 | coroutine, regardless of priority, once. |
347 | coroutine, regardless of priority. This is useful sometimes to ensure |
|
|
348 | progress is made. |
282 | |
349 | |
283 | =item terminate [arg...] |
350 | =item terminate [arg...] |
284 | |
351 | |
285 | Terminates the current coroutine with the given status values (see L<cancel>). |
352 | Terminates the current coroutine with the given status values (see L<cancel>). |
286 | |
353 | |
287 | =item killall |
354 | =item killall |
288 | |
355 | |
289 | Kills/terminates/cancels all coroutines except the currently running |
356 | Kills/terminates/cancels all coroutines except the currently running |
290 | one. This is useful after a fork, either in the child or the parent, as |
357 | one. This is useful after a fork, either in the child or the parent, as |
291 | usually only one of them should inherit the running coroutines. |
358 | usually only one of them should inherit the running coroutines. |
|
|
359 | |
|
|
360 | Note that while this will try to free some of the main programs resources, |
|
|
361 | you cnanot free all of them, so if a coroutine that is not the main |
|
|
362 | program calls this function, there will be some one-time resource leak. |
292 | |
363 | |
293 | =cut |
364 | =cut |
294 | |
365 | |
295 | sub terminate { |
366 | sub terminate { |
296 | $current->cancel (@_); |
367 | $current->cancel (@_); |
… | |
… | |
305 | |
376 | |
306 | =back |
377 | =back |
307 | |
378 | |
308 | =head2 COROUTINE METHODS |
379 | =head2 COROUTINE METHODS |
309 | |
380 | |
310 | These are the methods you can call on coroutine objects. |
381 | These are the methods you can call on coroutine objects (or to create |
|
|
382 | them). |
311 | |
383 | |
312 | =over 4 |
384 | =over 4 |
313 | |
385 | |
314 | =item new Coro \&sub [, @args...] |
386 | =item new Coro \&sub [, @args...] |
315 | |
387 | |
316 | Create a new coroutine and return it. When the sub returns the coroutine |
388 | Create a new coroutine and return it. When the sub returns, the coroutine |
317 | automatically terminates as if C<terminate> with the returned values were |
389 | automatically terminates as if C<terminate> with the returned values were |
318 | called. To make the coroutine run you must first put it into the ready queue |
390 | called. To make the coroutine run you must first put it into the ready |
319 | by calling the ready method. |
391 | queue by calling the ready method. |
320 | |
392 | |
321 | See C<async> and C<Coro::State::new> for additional info about the |
393 | See C<async> and C<Coro::State::new> for additional info about the |
322 | coroutine environment. |
394 | coroutine environment. |
323 | |
395 | |
324 | =cut |
396 | =cut |
… | |
… | |
333 | $class->SUPER::new (\&_run_coro, @_) |
405 | $class->SUPER::new (\&_run_coro, @_) |
334 | } |
406 | } |
335 | |
407 | |
336 | =item $success = $coroutine->ready |
408 | =item $success = $coroutine->ready |
337 | |
409 | |
338 | Put the given coroutine into the ready queue (according to it's priority) |
410 | Put the given coroutine into the end of its ready queue (there is one |
339 | and return true. If the coroutine is already in the ready queue, do nothing |
411 | queue for each priority) and return true. If the coroutine is already in |
340 | and return false. |
412 | the ready queue, do nothing and return false. |
|
|
413 | |
|
|
414 | This ensures that the scheduler will resume this coroutine automatically |
|
|
415 | once all the coroutines of higher priority and all coroutines of the same |
|
|
416 | priority that were put into the ready queue earlier have been resumed. |
341 | |
417 | |
342 | =item $is_ready = $coroutine->is_ready |
418 | =item $is_ready = $coroutine->is_ready |
343 | |
419 | |
344 | Return wether the coroutine is currently the ready queue or not, |
420 | Return wether the coroutine is currently the ready queue or not, |
345 | |
421 | |
… | |
… | |
366 | |
442 | |
367 | =item $coroutine->join |
443 | =item $coroutine->join |
368 | |
444 | |
369 | Wait until the coroutine terminates and return any values given to the |
445 | Wait until the coroutine terminates and return any values given to the |
370 | C<terminate> or C<cancel> functions. C<join> can be called concurrently |
446 | C<terminate> or C<cancel> functions. C<join> can be called concurrently |
371 | from multiple coroutines. |
447 | from multiple coroutines, and all will be resumed and given the status |
|
|
448 | return once the C<$coroutine> terminates. |
372 | |
449 | |
373 | =cut |
450 | =cut |
374 | |
451 | |
375 | sub join { |
452 | sub join { |
376 | my $self = shift; |
453 | my $self = shift; |
… | |
… | |
391 | |
468 | |
392 | =item $coroutine->on_destroy (\&cb) |
469 | =item $coroutine->on_destroy (\&cb) |
393 | |
470 | |
394 | Registers a callback that is called when this coroutine gets destroyed, |
471 | Registers a callback that is called when this coroutine gets destroyed, |
395 | but before it is joined. The callback gets passed the terminate arguments, |
472 | but before it is joined. The callback gets passed the terminate arguments, |
396 | if any. |
473 | if any, and I<must not> die, under any circumstances. |
397 | |
474 | |
398 | =cut |
475 | =cut |
399 | |
476 | |
400 | sub on_destroy { |
477 | sub on_destroy { |
401 | my ($self, $cb) = @_; |
478 | my ($self, $cb) = @_; |
… | |
… | |
469 | =over 4 |
546 | =over 4 |
470 | |
547 | |
471 | =item Coro::nready |
548 | =item Coro::nready |
472 | |
549 | |
473 | Returns the number of coroutines that are currently in the ready state, |
550 | Returns the number of coroutines that are currently in the ready state, |
474 | i.e. that can be switched to. The value C<0> means that the only runnable |
551 | i.e. that can be switched to by calling C<schedule> directory or |
|
|
552 | indirectly. The value C<0> means that the only runnable coroutine is the |
475 | coroutine is the currently running one, so C<cede> would have no effect, |
553 | currently running one, so C<cede> would have no effect, and C<schedule> |
476 | and C<schedule> would cause a deadlock unless there is an idle handler |
554 | would cause a deadlock unless there is an idle handler that wakes up some |
477 | that wakes up some coroutines. |
555 | coroutines. |
478 | |
556 | |
479 | =item my $guard = Coro::guard { ... } |
557 | =item my $guard = Coro::guard { ... } |
480 | |
558 | |
481 | This creates and returns a guard object. Nothing happens until the object |
559 | This creates and returns a guard object. Nothing happens until the object |
482 | gets destroyed, in which case the codeblock given as argument will be |
560 | gets destroyed, in which case the codeblock given as argument will be |
… | |
… | |
511 | |
589 | |
512 | |
590 | |
513 | =item unblock_sub { ... } |
591 | =item unblock_sub { ... } |
514 | |
592 | |
515 | This utility function takes a BLOCK or code reference and "unblocks" it, |
593 | This utility function takes a BLOCK or code reference and "unblocks" it, |
516 | returning the new coderef. This means that the new coderef will return |
594 | returning a new coderef. Unblocking means that calling the new coderef |
517 | immediately without blocking, returning nothing, while the original code |
595 | will return immediately without blocking, returning nothing, while the |
518 | ref will be called (with parameters) from within its own coroutine. |
596 | original code ref will be called (with parameters) from within another |
|
|
597 | coroutine. |
519 | |
598 | |
520 | The reason this function exists is that many event libraries (such as the |
599 | The reason this function exists is that many event libraries (such as the |
521 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
600 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
522 | of thread-safety). This means you must not block within event callbacks, |
601 | of thread-safety). This means you must not block within event callbacks, |
523 | otherwise you might suffer from crashes or worse. |
602 | otherwise you might suffer from crashes or worse. The only event library |
|
|
603 | currently known that is safe to use without C<unblock_sub> is L<EV>. |
524 | |
604 | |
525 | This function allows your callbacks to block by executing them in another |
605 | This function allows your callbacks to block by executing them in another |
526 | coroutine where it is safe to block. One example where blocking is handy |
606 | coroutine where it is safe to block. One example where blocking is handy |
527 | is when you use the L<Coro::AIO|Coro::AIO> functions to save results to |
607 | is when you use the L<Coro::AIO|Coro::AIO> functions to save results to |
528 | disk. |
608 | disk, for example. |
529 | |
609 | |
530 | In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when |
610 | In short: simply use C<unblock_sub { ... }> instead of C<sub { ... }> when |
531 | creating event callbacks that want to block. |
611 | creating event callbacks that want to block. |
|
|
612 | |
|
|
613 | If your handler does not plan to block (e.g. simply sends a message to |
|
|
614 | another coroutine, or puts some other coroutine into the ready queue), |
|
|
615 | there is no reason to use C<unblock_sub>. |
|
|
616 | |
|
|
617 | Note that you also need to use C<unblock_sub> for any other callbacks that |
|
|
618 | are indirectly executed by any C-based event loop. For example, when you |
|
|
619 | use a module that uses L<AnyEvent> (and you use L<Coro::AnyEvent>) and it |
|
|
620 | provides callbacks that are the result of some event callback, then you |
|
|
621 | must not block either, or use C<unblock_sub>. |
532 | |
622 | |
533 | =cut |
623 | =cut |
534 | |
624 | |
535 | our @unblock_queue; |
625 | our @unblock_queue; |
536 | |
626 | |
… | |
… | |
568 | |
658 | |
569 | 1; |
659 | 1; |
570 | |
660 | |
571 | =head1 BUGS/LIMITATIONS |
661 | =head1 BUGS/LIMITATIONS |
572 | |
662 | |
573 | - you must make very sure that no coro is still active on global |
|
|
574 | destruction. very bad things might happen otherwise (usually segfaults). |
|
|
575 | |
|
|
576 | - this module is not thread-safe. You should only ever use this module |
663 | This module is not perl-pseudo-thread-safe. You should only ever use this |
577 | from the same thread (this requirement might be loosened in the future |
664 | module from the same thread (this requirement might be removed in the |
578 | to allow per-thread schedulers, but Coro::State does not yet allow |
665 | future to allow per-thread schedulers, but Coro::State does not yet allow |
579 | this). |
666 | this). I recommend disabling thread support and using processes, as this |
|
|
667 | is much faster and uses less memory. |
580 | |
668 | |
581 | =head1 SEE ALSO |
669 | =head1 SEE ALSO |
582 | |
670 | |
583 | Lower level Configuration, Coroutine Environment: L<Coro::State>. |
671 | Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>. |
584 | |
672 | |
585 | Debugging: L<Coro::Debug>. |
673 | Debugging: L<Coro::Debug>. |
586 | |
674 | |
587 | Support/Utility: L<Coro::Specific>, L<Coro::Util>. |
675 | Support/Utility: L<Coro::Specific>, L<Coro::Util>. |
588 | |
676 | |
589 | Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
677 | Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
590 | |
678 | |
591 | Event/IO: L<Coro::Timer>, L<Coro::Event>, L<Coro::Handle>, L<Coro::Socket>. |
679 | IO/Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>. |
592 | |
680 | |
593 | Compatibility: L<Coro::LWP>, L<Coro::Storable>, L<Coro::Select>. |
681 | Compatibility: L<Coro::LWP>, L<Coro::BDB>, L<Coro::Storable>, L<Coro::Select>. |
594 | |
682 | |
595 | Embedding: L<Coro::MakeMaker>. |
683 | XS API: L<Coro::MakeMaker>. |
|
|
684 | |
|
|
685 | Low level Configuration, Coroutine Environment: L<Coro::State>. |
596 | |
686 | |
597 | =head1 AUTHOR |
687 | =head1 AUTHOR |
598 | |
688 | |
599 | Marc Lehmann <schmorp@schmorp.de> |
689 | Marc Lehmann <schmorp@schmorp.de> |
600 | http://home.schmorp.de/ |
690 | http://home.schmorp.de/ |