… | |
… | |
86 | 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 |
87 | whether you are running in the main program or not. |
87 | whether you are running in the main program or not. |
88 | |
88 | |
89 | =cut |
89 | =cut |
90 | |
90 | |
91 | $main = new Coro; |
91 | # $main is now being initialised by Coro::State |
92 | |
92 | |
93 | =item $Coro::current |
93 | =item $Coro::current |
94 | |
94 | |
95 | The coroutine object representing the current coroutine (the last |
95 | The coroutine object representing the current coroutine (the last |
96 | coroutine that the Coro scheduler switched to). The initial value is |
96 | coroutine that the Coro scheduler switched to). The initial value is |
97 | C<$main> (of course). |
97 | C<$Coro::main> (of course). |
98 | |
98 | |
99 | This variable is B<strictly> I<read-only>. You can take copies of the |
99 | This variable is B<strictly> I<read-only>. You can take copies of the |
100 | value stored in it and use it as any other coroutine object, but you must |
100 | value stored in it and use it as any other coroutine object, but you must |
101 | not otherwise modify the variable itself. |
101 | not otherwise modify the variable itself. |
102 | |
102 | |
103 | =cut |
103 | =cut |
104 | |
|
|
105 | $main->{desc} = "[main::]"; |
|
|
106 | |
|
|
107 | # maybe some other module used Coro::Specific before... |
|
|
108 | $main->{_specific} = $current->{_specific} |
|
|
109 | if $current; |
|
|
110 | |
|
|
111 | _set_current $main; |
|
|
112 | |
104 | |
113 | sub current() { $current } # [DEPRECATED] |
105 | sub current() { $current } # [DEPRECATED] |
114 | |
106 | |
115 | =item $Coro::idle |
107 | =item $Coro::idle |
116 | |
108 | |
… | |
… | |
444 | } |
436 | } |
445 | |
437 | |
446 | =item $coroutine->throw ([$scalar]) |
438 | =item $coroutine->throw ([$scalar]) |
447 | |
439 | |
448 | If C<$throw> is specified and defined, it will be thrown as an exception |
440 | 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 |
441 | inside the coroutine at the next convenient point in time. Otherwise |
450 | it gains control at the next schedule/transfer/cede). Otherwise clears the |
|
|
451 | exception object. |
442 | clears the exception object. |
|
|
443 | |
|
|
444 | Coro will check for the exception each time a schedule-like-function |
|
|
445 | returns, i.e. after each C<schedule>, C<cede>, C<< Coro::Semaphore->down |
|
|
446 | >>, C<< Coro::Handle->readable >> and so on. Note that this means that |
|
|
447 | when a coroutine is acquiring a lock, it might only throw after it has |
|
|
448 | sucessfully acquired it. |
452 | |
449 | |
453 | The exception object will be thrown "as is" with the specified scalar in |
450 | 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 |
451 | C<$@>, i.e. if it is a string, no line number or newline will be appended |
455 | (unlike with C<die>). |
452 | (unlike with C<die>). |
456 | |
453 | |
… | |
… | |
667 | |
664 | |
668 | =head1 BUGS/LIMITATIONS |
665 | =head1 BUGS/LIMITATIONS |
669 | |
666 | |
670 | =over 4 |
667 | =over 4 |
671 | |
668 | |
|
|
669 | =item fork with pthread backend |
|
|
670 | |
|
|
671 | When Coro is compiled using the pthread backend (which isn't recommended |
|
|
672 | but required on many BSDs as their libcs are completely broken), then |
|
|
673 | coroutines will not survive a fork. There is no known workaround except to |
|
|
674 | fix your libc and use a saner backend. |
|
|
675 | |
672 | =item perl process emulation ("threads") |
676 | =item perl process emulation ("threads") |
673 | |
677 | |
674 | This module is not perl-pseudo-thread-safe. You should only ever use this |
678 | This module is not perl-pseudo-thread-safe. You should only ever use this |
675 | module from the same thread (this requirement might be removed in the |
679 | module from the same thread (this requirement might be removed in the |
676 | future to allow per-thread schedulers, but Coro::State does not yet allow |
680 | future to allow per-thread schedulers, but Coro::State does not yet allow |
… | |
… | |
681 | =item coroutine switching not signal safe |
685 | =item coroutine switching not signal safe |
682 | |
686 | |
683 | You must not switch to another coroutine from within a signal handler |
687 | You must not switch to another coroutine from within a signal handler |
684 | (only relevant with %SIG - most event libraries provide safe signals). |
688 | (only relevant with %SIG - most event libraries provide safe signals). |
685 | |
689 | |
686 | That means you I<MUST NOT> call any fucntion that might "block" the |
690 | That means you I<MUST NOT> call any function that might "block" the |
687 | current coroutine - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or |
691 | current coroutine - C<cede>, C<schedule> C<< Coro::Semaphore->down >> or |
688 | anything that calls those. Everything else, including calling C<ready>, |
692 | anything that calls those. Everything else, including calling C<ready>, |
689 | works. |
693 | works. |
690 | |
694 | |
691 | =back |
695 | =back |