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.276 by root, Wed Apr 14 01:56:02 2010 UTC vs.
Revision 1.283 by root, Sat Feb 5 21:20:47 2011 UTC

… …
81 81
82our $idle; # idle handler 82our $idle; # idle handler
83our $main; # main coro 83our $main; # main coro
84our $current; # current coro 84our $current; # current coro
85 85
86our $VERSION = 5.22; 86our $VERSION = 5.25;
87 87
88our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait); 88our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub rouse_cb rouse_wait);
89our %EXPORT_TAGS = ( 89our %EXPORT_TAGS = (
90 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], 90 prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)],
91); 91);
… …
613Sets (or gets in case the argument is missing) the description for this 613Sets (or gets in case the argument is missing) the description for this
614coro. This is just a free-form string you can associate with a 614coro. This is just a free-form string you can associate with a
615coro. 615coro.
616 616
617This method simply sets the C<< $coro->{desc} >> member to the given 617This method simply sets the C<< $coro->{desc} >> member to the given
618string. You can modify this member directly if you wish. 618string. You can modify this member directly if you wish, and in fact, this
619is often preferred to indicate major processing states that cna then be
620seen for example in a L<Coro::Debug> session:
621
622 sub my_long_function {
623 local $Coro::current->{desc} = "now in my_long_function";
624 ...
625 $Coro::current->{desc} = "my_long_function: phase 1";
626 ...
627 $Coro::current->{desc} = "my_long_function: phase 2";
628 ...
629 }
619 630
620=cut 631=cut
621 632
622sub desc { 633sub desc {
623 my $old = $_[0]{desc}; 634 my $old = $_[0]{desc};
… …
660returning a new coderef. Unblocking means that calling the new coderef 671returning a new coderef. Unblocking means that calling the new coderef
661will return immediately without blocking, returning nothing, while the 672will return immediately without blocking, returning nothing, while the
662original code ref will be called (with parameters) from within another 673original code ref will be called (with parameters) from within another
663coro. 674coro.
664 675
665The reason this function exists is that many event libraries (such as the 676The reason this function exists is that many event libraries (such as
666venerable L<Event|Event> module) are not thread-safe (a weaker form 677the venerable L<Event|Event> module) are not thread-safe (a weaker form
667of reentrancy). This means you must not block within event callbacks, 678of reentrancy). This means you must not block within event callbacks,
668otherwise you might suffer from crashes or worse. The only event library 679otherwise you might suffer from crashes or worse. The only event library
669currently known that is safe to use without C<unblock_sub> is L<EV>. 680currently known that is safe to use without C<unblock_sub> is L<EV> (but
681you might still run into deadlocks if all event loops are blocked).
670 682
671Coro will try to catch you when you block in the event loop 683Coro will try to catch you when you block in the event loop
672("FATAL:$Coro::IDLE blocked itself"), but this is just best effort and 684("FATAL:$Coro::IDLE blocked itself"), but this is just best effort and
673only works when you do not run your own event loop. 685only works when you do not run your own event loop.
674 686
… …
745 757
746=back 758=back
747 759
748=cut 760=cut
749 761
762for my $module (qw(Channel RWLock Semaphore SemaphoreSet Signal Specific)) {
763 my $old = defined &{"Coro::$module\::new"} && \&{"Coro::$module\::new"};
764
765 *{"Coro::$module\::new"} = sub {
766 require "Coro/$module.pm";
767
768 # some modules have their new predefined in State.xs, some don't
769 *{"Coro::$module\::new"} = $old
770 if $old;
771
772 goto &{"Coro::$module\::new"};
773 };
774}
775
7501; 7761;
751 777
752=head1 HOW TO WAIT FOR A CALLBACK 778=head1 HOW TO WAIT FOR A CALLBACK
753 779
754It is very common for a coro to wait for some callback to be 780It is very common for a coro to wait for some callback to be
… …
857ithreads (for example, that memory or files would be shared), showing his 883ithreads (for example, that memory or files would be shared), showing his
858lack of understanding of this area - if it is hard to understand for Chip, 884lack of understanding of this area - if it is hard to understand for Chip,
859it is probably not obvious to everybody). 885it is probably not obvious to everybody).
860 886
861What follows is an ultra-condensed version of my talk about threads in 887What follows is an ultra-condensed version of my talk about threads in
862scripting languages given onthe perl workshop 2009: 888scripting languages given on the perl workshop 2009:
863 889
864The so-called "ithreads" were originally implemented for two reasons: 890The so-called "ithreads" were originally implemented for two reasons:
865first, to (badly) emulate unix processes on native win32 perls, and 891first, to (badly) emulate unix processes on native win32 perls, and
866secondly, to replace the older, real thread model ("5.005-threads"). 892secondly, to replace the older, real thread model ("5.005-threads").
867 893

Diff Legend

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