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

Comparing Coro/Coro.pm (file contents):
Revision 1.114 by root, Wed Jan 24 16:22:08 2007 UTC vs.
Revision 1.125 by root, Fri Apr 27 19:35:58 2007 UTC

… …
20 20
21=head1 DESCRIPTION 21=head1 DESCRIPTION
22 22
23This module collection manages coroutines. Coroutines are similar 23This module collection manages coroutines. Coroutines are similar
24to threads but don't run in parallel at the same time even on SMP 24to threads but don't run in parallel at the same time even on SMP
25machines. The specific flavor of coroutine use din this module also 25machines. The specific flavor of coroutine used in this module also
26guarentees you that it will not switch between coroutines unless 26guarantees you that it will not switch between coroutines unless
27necessary, at easily-identified points in your program, so locking and 27necessary, at easily-identified points in your program, so locking and
28parallel access are rarely an issue, making coroutine programming much 28parallel access are rarely an issue, making coroutine programming much
29safer than threads programming. 29safer than threads programming.
30 30
31(Perl, however, does not natively support real threads but instead does a 31(Perl, however, does not natively support real threads but instead does a
… …
50 50
51our $idle; # idle handler 51our $idle; # idle handler
52our $main; # main coroutine 52our $main; # main coroutine
53our $current; # current coroutine 53our $current; # current coroutine
54 54
55our $VERSION = '3.5'; 55our $VERSION = '3.62';
56 56
57our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); 57our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub);
58our %EXPORT_TAGS = ( 58our %EXPORT_TAGS = (
59 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], 59 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
60); 60);
… …
108 108
109The current coroutine (the last coroutine switched to). The initial value 109The current coroutine (the last coroutine switched to). The initial value
110is C<$main> (of course). 110is C<$main> (of course).
111 111
112This variable is B<strictly> I<read-only>. It is provided for performance 112This variable is B<strictly> I<read-only>. It is provided for performance
113reasons. If performance is not essentiel you are encouraged to use the 113reasons. If performance is not essential you are encouraged to use the
114C<Coro::current> function instead. 114C<Coro::current> function instead.
115 115
116=cut 116=cut
117 117
118# maybe some other module used Coro::Specific before... 118# maybe some other module used Coro::Specific before...
… …
185 185
186Create a new asynchronous coroutine and return it's coroutine object 186Create a new asynchronous coroutine and return it's coroutine object
187(usually unused). When the sub returns the new coroutine is automatically 187(usually unused). When the sub returns the new coroutine is automatically
188terminated. 188terminated.
189 189
190Calling C<exit> in a coroutine will not work correctly, so do not do that. 190Calling C<exit> in a coroutine will do the same as calling exit outside
191 191the coroutine. Likewise, when the coroutine dies, the program will exit,
192When the coroutine dies, the program will exit, just as in the main 192just as it would in the main program.
193program.
194 193
195 # create a new coroutine that just prints its arguments 194 # create a new coroutine that just prints its arguments
196 async { 195 async {
197 print "@_\n"; 196 print "@_\n";
198 } 1,2,3,4; 197 } 1,2,3,4;
… …
242 warn $@ if $@; 241 warn $@ if $@;
243 242
244 last if @pool >= $POOL_SIZE; 243 last if @pool >= $POOL_SIZE;
245 push @pool, $current; 244 push @pool, $current;
246 245
246 $current->save (Coro::State::SAVE_DEF);
247 $current->prio (0); 247 $current->prio (0);
248 schedule; 248 schedule;
249 } 249 }
250} 250}
251 251
… …
277 # wake up sleeping coroutine 277 # wake up sleeping coroutine
278 $current->ready; 278 $current->ready;
279 undef $current; 279 undef $current;
280 }; 280 };
281 281
282 # call schedule until event occured. 282 # call schedule until event occurred.
283 # in case we are woken up for other reasons 283 # in case we are woken up for other reasons
284 # (current still defined), loop. 284 # (current still defined), loop.
285 Coro::schedule while $current; 285 Coro::schedule while $current;
286 } 286 }
287 287
… …
325Create a new coroutine and return it. When the sub returns the coroutine 325Create a new coroutine and return it. When the sub returns the coroutine
326automatically terminates as if C<terminate> with the returned values were 326automatically terminates as if C<terminate> with the returned values were
327called. To make the coroutine run you must first put it into the ready queue 327called. To make the coroutine run you must first put it into the ready queue
328by calling the ready method. 328by calling the ready method.
329 329
330Calling C<exit> in a coroutine will not work correctly, so do not do that. 330See C<async> for additional discussion.
331 331
332=cut 332=cut
333 333
334sub _run_coro { 334sub _run_coro {
335 terminate &{+shift}; 335 terminate &{+shift};
… …
458=over 4 458=over 4
459 459
460=item Coro::nready 460=item Coro::nready
461 461
462Returns the number of coroutines that are currently in the ready state, 462Returns the number of coroutines that are currently in the ready state,
463i.e. that can be swicthed to. The value C<0> means that the only runnable 463i.e. that can be switched to. The value C<0> means that the only runnable
464coroutine is the currently running one, so C<cede> would have no effect, 464coroutine is the currently running one, so C<cede> would have no effect,
465and C<schedule> would cause a deadlock unless there is an idle handler 465and C<schedule> would cause a deadlock unless there is an idle handler
466that wakes up some coroutines. 466that wakes up some coroutines.
467 467
468=item my $guard = Coro::guard { ... } 468=item my $guard = Coro::guard { ... }
469 469
470This creates and returns a guard object. Nothing happens until the objetc 470This creates and returns a guard object. Nothing happens until the object
471gets destroyed, in which case the codeblock given as argument will be 471gets destroyed, in which case the codeblock given as argument will be
472executed. This is useful to free locks or other resources in case of a 472executed. This is useful to free locks or other resources in case of a
473runtime error or when the coroutine gets canceled, as in both cases the 473runtime error or when the coroutine gets canceled, as in both cases the
474guard block will be executed. The guard object supports only one method, 474guard block will be executed. The guard object supports only one method,
475C<< ->cancel >>, which will keep the codeblock from being executed. 475C<< ->cancel >>, which will keep the codeblock from being executed.
… …
504This utility function takes a BLOCK or code reference and "unblocks" it, 504This utility function takes a BLOCK or code reference and "unblocks" it,
505returning the new coderef. This means that the new coderef will return 505returning the new coderef. This means that the new coderef will return
506immediately without blocking, returning nothing, while the original code 506immediately without blocking, returning nothing, while the original code
507ref will be called (with parameters) from within its own coroutine. 507ref will be called (with parameters) from within its own coroutine.
508 508
509The reason this fucntion exists is that many event libraries (such as the 509The reason this function exists is that many event libraries (such as the
510venerable L<Event|Event> module) are not coroutine-safe (a weaker form 510venerable L<Event|Event> module) are not coroutine-safe (a weaker form
511of thread-safety). This means you must not block within event callbacks, 511of thread-safety). This means you must not block within event callbacks,
512otherwise you might suffer from crashes or worse. 512otherwise you might suffer from crashes or worse.
513 513
514This function allows your callbacks to block by executing them in another 514This function allows your callbacks to block by executing them in another
… …
560 560
561 - you must make very sure that no coro is still active on global 561 - you must make very sure that no coro is still active on global
562 destruction. very bad things might happen otherwise (usually segfaults). 562 destruction. very bad things might happen otherwise (usually segfaults).
563 563
564 - this module is not thread-safe. You should only ever use this module 564 - this module is not thread-safe. You should only ever use this module
565 from the same thread (this requirement might be losened in the future 565 from the same thread (this requirement might be loosened in the future
566 to allow per-thread schedulers, but Coro::State does not yet allow 566 to allow per-thread schedulers, but Coro::State does not yet allow
567 this). 567 this).
568 568
569=head1 SEE ALSO 569=head1 SEE ALSO
570 570

Diff Legend

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