… | |
… | |
16 | cede; # yield to coroutine |
16 | cede; # yield to coroutine |
17 | print "3\n"; |
17 | print "3\n"; |
18 | cede; # and again |
18 | cede; # and again |
19 | |
19 | |
20 | # use locking |
20 | # use locking |
|
|
21 | use Coro::Semaphore; |
21 | my $lock = new Coro::Semaphore; |
22 | my $lock = new Coro::Semaphore; |
22 | my $locked; |
23 | my $locked; |
23 | |
24 | |
24 | $lock->down; |
25 | $lock->down; |
25 | $locked = 1; |
26 | $locked = 1; |
… | |
… | |
55 | |
56 | |
56 | =cut |
57 | =cut |
57 | |
58 | |
58 | package Coro; |
59 | package Coro; |
59 | |
60 | |
60 | use strict; |
61 | use strict qw(vars subs); |
61 | no warnings "uninitialized"; |
62 | no warnings "uninitialized"; |
62 | |
63 | |
63 | use Coro::State; |
64 | use Coro::State; |
64 | |
65 | |
65 | use base qw(Coro::State Exporter); |
66 | use base qw(Coro::State Exporter); |
66 | |
67 | |
67 | our $idle; # idle handler |
68 | our $idle; # idle handler |
68 | our $main; # main coroutine |
69 | our $main; # main coroutine |
69 | our $current; # current coroutine |
70 | our $current; # current coroutine |
70 | |
71 | |
71 | our $VERSION = 4.743; |
72 | our $VERSION = 5.0; |
72 | |
73 | |
73 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
74 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
74 | our %EXPORT_TAGS = ( |
75 | our %EXPORT_TAGS = ( |
75 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
76 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
76 | ); |
77 | ); |
… | |
… | |
81 | =item $Coro::main |
82 | =item $Coro::main |
82 | |
83 | |
83 | This variable stores the coroutine object that represents the main |
84 | 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 | 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 | coroutines, it is mainly useful to compare again C<$Coro::current>, to see |
86 | wether you are running in the main program or not. |
87 | whether you are running in the main program or not. |
87 | |
88 | |
88 | =cut |
89 | =cut |
89 | |
90 | |
90 | $main = new Coro; |
91 | $main = new Coro; |
91 | |
92 | |
… | |
… | |
151 | $self->_destroy |
152 | $self->_destroy |
152 | or return; |
153 | or return; |
153 | |
154 | |
154 | # call all destruction callbacks |
155 | # call all destruction callbacks |
155 | $_->(@{$self->{_status}}) |
156 | $_->(@{$self->{_status}}) |
156 | for @{(delete $self->{_on_destroy}) || []}; |
157 | for @{ delete $self->{_on_destroy} || [] }; |
157 | } |
158 | } |
158 | |
159 | |
159 | # this coroutine is necessary because a coroutine |
160 | # this coroutine is necessary because a coroutine |
160 | # cannot destroy itself. |
161 | # cannot destroy itself. |
161 | my @destroy; |
162 | my @destroy; |
… | |
… | |
167 | while @destroy; |
168 | while @destroy; |
168 | |
169 | |
169 | &schedule; |
170 | &schedule; |
170 | } |
171 | } |
171 | }; |
172 | }; |
172 | $manager->desc ("[coro manager]"); |
173 | $manager->{desc} = "[coro manager]"; |
173 | $manager->prio (PRIO_MAX); |
174 | $manager->prio (PRIO_MAX); |
174 | |
175 | |
175 | =back |
176 | =back |
176 | |
177 | |
177 | =head2 SIMPLE COROUTINE CREATION |
178 | =head2 SIMPLE COROUTINE CREATION |
… | |
… | |
220 | terminate or join on it (although you are allowed to), and you get a |
221 | terminate or join on it (although you are allowed to), and you get a |
221 | coroutine that might have executed other code already (which can be good |
222 | coroutine that might have executed other code already (which can be good |
222 | or bad :). |
223 | or bad :). |
223 | |
224 | |
224 | On the plus side, this function is faster than creating (and destroying) |
225 | 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 | a completly new coroutine, so if you need a lot of generic coroutines in |
226 | quick successsion, use C<async_pool>, not C<async>. |
227 | quick successsion, use C<async_pool>, not C<async>. |
227 | |
228 | |
228 | The code block is executed in an C<eval> context and a warning will be |
229 | The code block is executed in an C<eval> context and a warning will be |
229 | issued in case of an exception instead of terminating the program, as |
230 | issued in case of an exception instead of terminating the program, as |
230 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
231 | C<async> does. As the coroutine is being reused, stuff like C<on_destroy> |
… | |
… | |
234 | |
235 | |
235 | The priority will be reset to C<0> after each run, tracing will be |
236 | The priority will be reset to C<0> after each run, tracing will be |
236 | disabled, the description will be reset and the default output filehandle |
237 | disabled, the description will be reset and the default output filehandle |
237 | gets restored, so you can change all these. Otherwise the coroutine will |
238 | gets restored, so you can change all these. Otherwise the coroutine will |
238 | be re-used "as-is": most notably if you change other per-coroutine global |
239 | be re-used "as-is": most notably if you change other per-coroutine global |
239 | stuff such as C<$/> you I<must needs> to revert that change, which is most |
240 | stuff such as C<$/> you I<must needs> revert that change, which is most |
240 | simply done by using local as in: C< local $/ >. |
241 | simply done by using local as in: C<< local $/ >>. |
241 | |
242 | |
242 | The pool size is limited to C<8> idle coroutines (this can be adjusted by |
243 | The idle pool size is limited to C<8> idle coroutines (this can be |
243 | changing $Coro::POOL_SIZE), and there can be as many non-idle coros as |
244 | adjusted by changing $Coro::POOL_SIZE), but there can be as many non-idle |
244 | required. |
245 | coros as required. |
245 | |
246 | |
246 | If you are concerned about pooled coroutines growing a lot because a |
247 | If you are concerned about pooled coroutines growing a lot because a |
247 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
248 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
248 | { terminate }> once per second or so to slowly replenish the pool. In |
249 | { terminate }> once per second or so to slowly replenish the pool. In |
249 | addition to that, when the stacks used by a handler grows larger than 16kb |
250 | addition to that, when the stacks used by a handler grows larger than 16kb |
… | |
… | |
274 | } |
275 | } |
275 | } |
276 | } |
276 | } |
277 | } |
277 | |
278 | |
278 | sub async_pool(&@) { |
279 | sub async_pool(&@) { |
279 | # this is also inlined into the unlock_scheduler |
280 | # this is also inlined into the unblock_scheduler |
280 | my $coro = (pop @async_pool) || new Coro \&pool_handler; |
281 | my $coro = (pop @async_pool) || new Coro \&pool_handler; |
281 | |
282 | |
282 | $coro->{_invoke} = [@_]; |
283 | $coro->{_invoke} = [@_]; |
283 | $coro->ready; |
284 | $coro->ready; |
284 | |
285 | |
… | |
… | |
309 | This makes C<schedule> I<the> generic method to use to block the current |
310 | This makes C<schedule> I<the> generic method to use to block the current |
310 | coroutine and wait for events: first you remember the current coroutine in |
311 | coroutine and wait for events: first you remember the current coroutine in |
311 | a variable, then arrange for some callback of yours to call C<< ->ready |
312 | a variable, then arrange for some callback of yours to call C<< ->ready |
312 | >> on that once some event happens, and last you call C<schedule> to put |
313 | >> on that once some event happens, and last you call C<schedule> to put |
313 | yourself to sleep. Note that a lot of things can wake your coroutine up, |
314 | yourself to sleep. Note that a lot of things can wake your coroutine up, |
314 | so you need to check wether the event indeed happened, e.g. by storing the |
315 | so you need to check whether the event indeed happened, e.g. by storing the |
315 | status in a variable. |
316 | status in a variable. |
316 | |
317 | |
317 | The canonical way to wait on external events is this: |
318 | The canonical way to wait on external events is this: |
318 | |
319 | |
319 | { |
320 | { |
… | |
… | |
358 | Kills/terminates/cancels all coroutines except the currently running |
359 | Kills/terminates/cancels all coroutines except the currently running |
359 | one. This is useful after a fork, either in the child or the parent, as |
360 | one. This is useful after a fork, either in the child or the parent, as |
360 | usually only one of them should inherit the running coroutines. |
361 | usually only one of them should inherit the running coroutines. |
361 | |
362 | |
362 | Note that while this will try to free some of the main programs resources, |
363 | Note that while this will try to free some of the main programs resources, |
363 | you cnanot free all of them, so if a coroutine that is not the main |
364 | you cannot free all of them, so if a coroutine that is not the main |
364 | program calls this function, there will be some one-time resource leak. |
365 | program calls this function, there will be some one-time resource leak. |
365 | |
366 | |
366 | =cut |
367 | =cut |
367 | |
368 | |
368 | sub terminate { |
369 | sub terminate { |
… | |
… | |
417 | once all the coroutines of higher priority and all coroutines of the same |
418 | once all the coroutines of higher priority and all coroutines of the same |
418 | priority that were put into the ready queue earlier have been resumed. |
419 | priority that were put into the ready queue earlier have been resumed. |
419 | |
420 | |
420 | =item $is_ready = $coroutine->is_ready |
421 | =item $is_ready = $coroutine->is_ready |
421 | |
422 | |
422 | Return wether the coroutine is currently the ready queue or not, |
423 | Return whether the coroutine is currently the ready queue or not, |
423 | |
424 | |
424 | =item $coroutine->cancel (arg...) |
425 | =item $coroutine->cancel (arg...) |
425 | |
426 | |
426 | Terminates the given coroutine and makes it return the given arguments as |
427 | Terminates the given coroutine and makes it return the given arguments as |
427 | status (default: the empty list). Never returns if the coroutine is the |
428 | status (default: the empty list). Never returns if the coroutine is the |
… | |
… | |
440 | } else { |
441 | } else { |
441 | $self->_cancel; |
442 | $self->_cancel; |
442 | } |
443 | } |
443 | } |
444 | } |
444 | |
445 | |
|
|
446 | =item $coroutine->throw ([$scalar]) |
|
|
447 | |
|
|
448 | If C<$throw> is specified and defined, it will be thrown as an exception |
|
|
449 | inside the coroutine at the next convenient point in time (usually after |
|
|
450 | it gains control at the next schedule/transfer/cede). Otherwise clears the |
|
|
451 | exception object. |
|
|
452 | |
|
|
453 | The exception object will be thrown "as is" with the specified scalar in |
|
|
454 | C<$@>, i.e. if it is a string, no line number or newline will be appended |
|
|
455 | (unlike with C<die>). |
|
|
456 | |
|
|
457 | This can be used as a softer means than C<cancel> to ask a coroutine to |
|
|
458 | end itself, although there is no guarantee that the exception will lead to |
|
|
459 | termination, and if the exception isn't caught it might well end the whole |
|
|
460 | program. |
|
|
461 | |
|
|
462 | You might also think of C<throw> as being the moral equivalent of |
|
|
463 | C<kill>ing a coroutine with a signal (in this case, a scalar). |
|
|
464 | |
445 | =item $coroutine->join |
465 | =item $coroutine->join |
446 | |
466 | |
447 | Wait until the coroutine terminates and return any values given to the |
467 | Wait until the coroutine terminates and return any values given to the |
448 | C<terminate> or C<cancel> functions. C<join> can be called concurrently |
468 | C<terminate> or C<cancel> functions. C<join> can be called concurrently |
449 | from multiple coroutines, and all will be resumed and given the status |
469 | from multiple coroutines, and all will be resumed and given the status |
… | |
… | |
510 | higher values mean lower priority, just as in unix). |
530 | higher values mean lower priority, just as in unix). |
511 | |
531 | |
512 | =item $olddesc = $coroutine->desc ($newdesc) |
532 | =item $olddesc = $coroutine->desc ($newdesc) |
513 | |
533 | |
514 | Sets (or gets in case the argument is missing) the description for this |
534 | Sets (or gets in case the argument is missing) the description for this |
515 | coroutine. This is just a free-form string you can associate with a coroutine. |
535 | coroutine. This is just a free-form string you can associate with a |
|
|
536 | coroutine. |
516 | |
537 | |
517 | This method simply sets the C<< $coroutine->{desc} >> member to the given string. You |
538 | This method simply sets the C<< $coroutine->{desc} >> member to the given |
518 | can modify this member directly if you wish. |
539 | string. You can modify this member directly if you wish. |
519 | |
|
|
520 | =item $coroutine->throw ([$scalar]) |
|
|
521 | |
|
|
522 | If C<$throw> is specified and defined, it will be thrown as an exception |
|
|
523 | inside the coroutine at the next convinient point in time (usually after |
|
|
524 | it gains control at the next schedule/transfer/cede). Otherwise clears the |
|
|
525 | exception object. |
|
|
526 | |
|
|
527 | The exception object will be thrown "as is" with the specified scalar in |
|
|
528 | C<$@>, i.e. if it is a string, no line number or newline will be appended |
|
|
529 | (unlike with C<die>). |
|
|
530 | |
|
|
531 | This can be used as a softer means than C<cancel> to ask a coroutine to |
|
|
532 | end itself, although there is no guarentee that the exception will lead to |
|
|
533 | termination, and if the exception isn't caught it might well end the whole |
|
|
534 | program. |
|
|
535 | |
540 | |
536 | =cut |
541 | =cut |
537 | |
542 | |
538 | sub desc { |
543 | sub desc { |
539 | my $old = $_[0]{desc}; |
544 | my $old = $_[0]{desc}; |
… | |
… | |
641 | cede; # for short-lived callbacks, this reduces pressure on the coro pool |
646 | cede; # for short-lived callbacks, this reduces pressure on the coro pool |
642 | } |
647 | } |
643 | schedule; # sleep well |
648 | schedule; # sleep well |
644 | } |
649 | } |
645 | }; |
650 | }; |
646 | $unblock_scheduler->desc ("[unblock_sub scheduler]"); |
651 | $unblock_scheduler->{desc} = "[unblock_sub scheduler]"; |
647 | |
652 | |
648 | sub unblock_sub(&) { |
653 | sub unblock_sub(&) { |
649 | my $cb = shift; |
654 | my $cb = shift; |
650 | |
655 | |
651 | sub { |
656 | sub { |
… | |
… | |
660 | |
665 | |
661 | 1; |
666 | 1; |
662 | |
667 | |
663 | =head1 BUGS/LIMITATIONS |
668 | =head1 BUGS/LIMITATIONS |
664 | |
669 | |
|
|
670 | =over 4 |
|
|
671 | |
|
|
672 | =item fork with pthread backend |
|
|
673 | |
|
|
674 | When Coro is compiled using the pthread backend (which isn't recommended |
|
|
675 | but required on many BSDs as their libcs are completely broken), then |
|
|
676 | coroutines will not survive a fork. There is no known workaround except to |
|
|
677 | fix your libc and use a saner backend. |
|
|
678 | |
|
|
679 | =item perl process emulation ("threads") |
|
|
680 | |
665 | This module is not perl-pseudo-thread-safe. You should only ever use this |
681 | This module is not perl-pseudo-thread-safe. You should only ever use this |
666 | module from the same thread (this requirement might be removed in the |
682 | module from the same thread (this requirement might be removed in the |
667 | future to allow per-thread schedulers, but Coro::State does not yet allow |
683 | future to allow per-thread schedulers, but Coro::State does not yet allow |
668 | this). I recommend disabling thread support and using processes, as this |
684 | this). I recommend disabling thread support and using processes, as having |
669 | is much faster and uses less memory. |
685 | the windows process emulation enabled under unix roughly halves perl |
|
|
686 | performance, even when not used. |
|
|
687 | |
|
|
688 | =item coroutine switching not signal safe |
|
|
689 | |
|
|
690 | You must not switch to another coroutine from within a signal handler |
|
|
691 | (only relevant with %SIG - most event libraries provide safe signals). |
|
|
692 | |
|
|
693 | That means you I<MUST NOT> call any fucntion that might "block" the |
|
|
694 | current coroutine - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or |
|
|
695 | anything that calls those. Everything else, including calling C<ready>, |
|
|
696 | works. |
|
|
697 | |
|
|
698 | =back |
|
|
699 | |
670 | |
700 | |
671 | =head1 SEE ALSO |
701 | =head1 SEE ALSO |
672 | |
702 | |
673 | Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>. |
703 | Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>. |
674 | |
704 | |