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

Comparing cvsroot/Coro/Coro.pm (file contents):
Revision 1.217 by root, Fri Nov 14 23:48:10 2008 UTC vs.
Revision 1.220 by root, Sun Nov 16 11:12:57 2008 UTC

… …
86coroutines, it is mainly useful to compare again C<$Coro::current>, to see 86coroutines, it is mainly useful to compare again C<$Coro::current>, to see
87whether you are running in the main program or not. 87whether 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
95The coroutine object representing the current coroutine (the last 95The coroutine object representing the current coroutine (the last
96coroutine that the Coro scheduler switched to). The initial value is 96coroutine that the Coro scheduler switched to). The initial value is
97C<$main> (of course). 97C<$Coro::main> (of course).
98 98
99This variable is B<strictly> I<read-only>. You can take copies of the 99This variable is B<strictly> I<read-only>. You can take copies of the
100value stored in it and use it as any other coroutine object, but you must 100value stored in it and use it as any other coroutine object, but you must
101not otherwise modify the variable itself. 101not 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
113sub current() { $current } # [DEPRECATED] 105sub current() { $current } # [DEPRECATED]
114 106
115=item $Coro::idle 107=item $Coro::idle
116 108
… …
275 } 267 }
276 } 268 }
277} 269}
278 270
279sub async_pool(&@) { 271sub async_pool(&@) {
280 # this is also inlined into the unlock_scheduler 272 # this is also inlined into the unblock_scheduler
281 my $coro = (pop @async_pool) || new Coro \&pool_handler; 273 my $coro = (pop @async_pool) || new Coro \&pool_handler;
282 274
283 $coro->{_invoke} = [@_]; 275 $coro->{_invoke} = [@_];
284 $coro->ready; 276 $coro->ready;
285 277
… …
667 659
668=head1 BUGS/LIMITATIONS 660=head1 BUGS/LIMITATIONS
669 661
670=over 4 662=over 4
671 663
664=item fork with pthread backend
665
666When Coro is compiled using the pthread backend (which isn't recommended
667but required on many BSDs as their libcs are completely broken), then
668coroutines will not survive a fork. There is no known workaround except to
669fix your libc and use a saner backend.
670
672=item perl process emulation ("threads") 671=item perl process emulation ("threads")
673 672
674This module is not perl-pseudo-thread-safe. You should only ever use this 673This module is not perl-pseudo-thread-safe. You should only ever use this
675module from the same thread (this requirement might be removed in the 674module from the same thread (this requirement might be removed in the
676future to allow per-thread schedulers, but Coro::State does not yet allow 675future to allow per-thread schedulers, but Coro::State does not yet allow

Diff Legend

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