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

Comparing Coro/Coro.pm (file contents):
Revision 1.118 by root, Mon Mar 19 15:50:48 2007 UTC vs.
Revision 1.121 by root, Fri Apr 13 12:56:55 2007 UTC

… …
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.55'; 55our $VERSION = '3.56';
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);
… …
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 try to do the same as calling exit
191outside the coroutine, but this is experimental. It is best not to rely on
192exit doing any cleanups or even not crashing.
191 193
192When the coroutine dies, the program will exit, just as in the main 194When the coroutine dies, the program will exit, just as in the main
193program. 195program.
194 196
195 # create a new coroutine that just prints its arguments 197 # create a new coroutine that just prints its arguments
… …
326Create a new coroutine and return it. When the sub returns the coroutine 328Create a new coroutine and return it. When the sub returns the coroutine
327automatically terminates as if C<terminate> with the returned values were 329automatically terminates as if C<terminate> with the returned values were
328called. To make the coroutine run you must first put it into the ready queue 330called. To make the coroutine run you must first put it into the ready queue
329by calling the ready method. 331by calling the ready method.
330 332
331Calling C<exit> in a coroutine will not work correctly, so do not do that. 333See C<async> for additional discussion.
332 334
333=cut 335=cut
334 336
335sub _run_coro { 337sub _run_coro {
336 terminate &{+shift}; 338 terminate &{+shift};
… …
466and C<schedule> would cause a deadlock unless there is an idle handler 468and C<schedule> would cause a deadlock unless there is an idle handler
467that wakes up some coroutines. 469that wakes up some coroutines.
468 470
469=item my $guard = Coro::guard { ... } 471=item my $guard = Coro::guard { ... }
470 472
471This creates and returns a guard object. Nothing happens until the objetc 473This creates and returns a guard object. Nothing happens until the object
472gets destroyed, in which case the codeblock given as argument will be 474gets destroyed, in which case the codeblock given as argument will be
473executed. This is useful to free locks or other resources in case of a 475executed. This is useful to free locks or other resources in case of a
474runtime error or when the coroutine gets canceled, as in both cases the 476runtime error or when the coroutine gets canceled, as in both cases the
475guard block will be executed. The guard object supports only one method, 477guard block will be executed. The guard object supports only one method,
476C<< ->cancel >>, which will keep the codeblock from being executed. 478C<< ->cancel >>, which will keep the codeblock from being executed.

Diff Legend

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