| … | |
… | |
| 665 | |
665 | |
| 666 | 1; |
666 | 1; |
| 667 | |
667 | |
| 668 | =head1 BUGS/LIMITATIONS |
668 | =head1 BUGS/LIMITATIONS |
| 669 | |
669 | |
|
|
670 | =over 4 |
|
|
671 | |
|
|
672 | =item perl process emulation ("threads") |
|
|
673 | |
| 670 | This module is not perl-pseudo-thread-safe. You should only ever use this |
674 | This module is not perl-pseudo-thread-safe. You should only ever use this |
| 671 | module from the same thread (this requirement might be removed in the |
675 | module from the same thread (this requirement might be removed in the |
| 672 | future to allow per-thread schedulers, but Coro::State does not yet allow |
676 | future to allow per-thread schedulers, but Coro::State does not yet allow |
| 673 | this). I recommend disabling thread support and using processes, as this |
677 | this). I recommend disabling thread support and using processes, as having |
| 674 | is much faster and uses less memory. |
678 | the windows process emulation enabled under unix roughly halves perl |
|
|
679 | performance, even when not used. |
|
|
680 | |
|
|
681 | =item coroutine switching not signal safe |
|
|
682 | |
|
|
683 | You must not switch to another coroutine from within a signal handler |
|
|
684 | (only relevant with %SIG - most event libraries provide safe signals). |
|
|
685 | |
|
|
686 | That means you I<MUST NOT> call any fucntion that might "block" the |
|
|
687 | current coroutine - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or |
|
|
688 | anything that calls those. Everything else, including calling C<ready>, |
|
|
689 | works. |
|
|
690 | |
|
|
691 | =back |
|
|
692 | |
| 675 | |
693 | |
| 676 | =head1 SEE ALSO |
694 | =head1 SEE ALSO |
| 677 | |
695 | |
| 678 | Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>. |
696 | Event-Loop integration: L<Coro::AnyEvent>, L<Coro::EV>, L<Coro::Event>. |
| 679 | |
697 | |
