1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | Coro - coroutine process abstraction |
3 | Coro - the only real threads in perl |
4 | |
4 | |
5 | =head1 SYNOPSIS |
5 | =head1 SYNOPSIS |
6 | |
6 | |
7 | use Coro; |
7 | use Coro; |
8 | |
8 | |
… | |
… | |
26 | $locked = 1; |
26 | $locked = 1; |
27 | $lock->up; |
27 | $lock->up; |
28 | |
28 | |
29 | =head1 DESCRIPTION |
29 | =head1 DESCRIPTION |
30 | |
30 | |
31 | This module collection manages coroutines. Coroutines are similar to |
31 | For a tutorial-style introduction, please read the L<Coro::Intro> |
32 | threads but don't (in general) run in parallel at the same time even |
32 | manpage. This manpage mainly contains reference information. |
33 | on SMP machines. The specific flavor of coroutine used in this module |
|
|
34 | also guarantees you that it will not switch between coroutines unless |
|
|
35 | necessary, at easily-identified points in your program, so locking and |
|
|
36 | parallel access are rarely an issue, making coroutine programming much |
|
|
37 | safer and easier than threads programming. |
|
|
38 | |
33 | |
39 | Unlike a normal perl program, however, coroutines allow you to have |
34 | This module collection manages continuations in general, most often |
40 | multiple running interpreters that share data, which is especially useful |
35 | in the form of cooperative threads (also called coroutines in the |
41 | to code pseudo-parallel processes and for event-based programming, such as |
36 | documentation). They are similar to kernel threads but don't (in general) |
42 | multiple HTTP-GET requests running concurrently. See L<Coro::AnyEvent> to |
37 | run in parallel at the same time even on SMP machines. The specific flavor |
43 | learn more. |
38 | of thread offered by this module also guarantees you that it will not |
|
|
39 | switch between threads unless necessary, at easily-identified points in |
|
|
40 | your program, so locking and parallel access are rarely an issue, making |
|
|
41 | thread programming much safer and easier than using other thread models. |
44 | |
42 | |
45 | Coroutines are also useful because Perl has no support for threads (the so |
43 | Unlike the so-called "Perl threads" (which are not actually real threads |
46 | called "threads" that perl offers are nothing more than the (bad) process |
44 | but only the windows process emulation ported to unix), Coro provides a |
47 | emulation coming from the Windows platform: On standard operating systems |
45 | full shared address space, which makes communication between threads |
48 | they serve no purpose whatsoever, except by making your programs slow and |
46 | very easy. And threads are fast, too: disabling the Windows process |
49 | making them use a lot of memory. Best disable them when building perl, or |
47 | emulation code in your perl and using Coro can easily result in a two to |
50 | aks your software vendor/distributor to do it for you). |
48 | four times speed increase for your programs. |
51 | |
49 | |
|
|
50 | Coro achieves that by supporting multiple running interpreters that share |
|
|
51 | data, which is especially useful to code pseudo-parallel processes and |
|
|
52 | for event-based programming, such as multiple HTTP-GET requests running |
|
|
53 | concurrently. See L<Coro::AnyEvent> to learn more on how to integrate Coro |
|
|
54 | into an event-based environment. |
|
|
55 | |
52 | In this module, coroutines are defined as "callchain + lexical variables + |
56 | In this module, a thread is defined as "callchain + lexical variables + |
53 | @_ + $_ + $@ + $/ + C stack), that is, a coroutine has its own callchain, |
57 | @_ + $_ + $@ + $/ + C stack), that is, a thread has its own callchain, |
54 | its own set of lexicals and its own set of perls most important global |
58 | its own set of lexicals and its own set of perls most important global |
55 | variables (see L<Coro::State> for more configuration). |
59 | variables (see L<Coro::State> for more configuration and background info). |
|
|
60 | |
|
|
61 | See also the C<SEE ALSO> section at the end of this document - the Coro |
|
|
62 | module family is quite large. |
56 | |
63 | |
57 | =cut |
64 | =cut |
58 | |
65 | |
59 | package Coro; |
66 | package Coro; |
60 | |
67 | |
61 | use strict qw(vars subs); |
68 | use strict qw(vars subs); |
62 | no warnings "uninitialized"; |
69 | no warnings "uninitialized"; |
|
|
70 | |
|
|
71 | use Guard (); |
63 | |
72 | |
64 | use Coro::State; |
73 | use Coro::State; |
65 | |
74 | |
66 | use base qw(Coro::State Exporter); |
75 | use base qw(Coro::State Exporter); |
67 | |
76 | |
68 | our $idle; # idle handler |
77 | our $idle; # idle handler |
69 | our $main; # main coroutine |
78 | our $main; # main coroutine |
70 | our $current; # current coroutine |
79 | our $current; # current coroutine |
71 | |
80 | |
72 | our $VERSION = "5.0"; |
81 | our $VERSION = 5.13; |
73 | |
82 | |
74 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
83 | our @EXPORT = qw(async async_pool cede schedule terminate current unblock_sub); |
75 | our %EXPORT_TAGS = ( |
84 | our %EXPORT_TAGS = ( |
76 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
85 | prio => [qw(PRIO_MAX PRIO_HIGH PRIO_NORMAL PRIO_LOW PRIO_IDLE PRIO_MIN)], |
77 | ); |
86 | ); |
78 | our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready)); |
87 | our @EXPORT_OK = (@{$EXPORT_TAGS{prio}}, qw(nready)); |
79 | |
88 | |
|
|
89 | =head1 GLOBAL VARIABLES |
|
|
90 | |
80 | =over 4 |
91 | =over 4 |
81 | |
92 | |
82 | =item $Coro::main |
93 | =item $Coro::main |
83 | |
94 | |
84 | This variable stores the coroutine object that represents the main |
95 | This variable stores the coroutine object that represents the main |
… | |
… | |
105 | sub current() { $current } # [DEPRECATED] |
116 | sub current() { $current } # [DEPRECATED] |
106 | |
117 | |
107 | =item $Coro::idle |
118 | =item $Coro::idle |
108 | |
119 | |
109 | This variable is mainly useful to integrate Coro into event loops. It is |
120 | This variable is mainly useful to integrate Coro into event loops. It is |
110 | usually better to rely on L<Coro::AnyEvent> or LC<Coro::EV>, as this is |
121 | usually better to rely on L<Coro::AnyEvent> or L<Coro::EV>, as this is |
111 | pretty low-level functionality. |
122 | pretty low-level functionality. |
112 | |
123 | |
113 | This variable stores a callback that is called whenever the scheduler |
124 | This variable stores either a coroutine or a callback. |
|
|
125 | |
|
|
126 | If it is a callback, the it is called whenever the scheduler finds no |
114 | finds no ready coroutines to run. The default implementation prints |
127 | ready coroutines to run. The default implementation prints "FATAL: |
115 | "FATAL: deadlock detected" and exits, because the program has no other way |
128 | deadlock detected" and exits, because the program has no other way to |
116 | to continue. |
129 | continue. |
117 | |
130 | |
|
|
131 | If it is a coroutine object, then this object will be readied (without |
|
|
132 | invoking any ready hooks, however) when the scheduler finds no other ready |
|
|
133 | coroutines to run. |
|
|
134 | |
118 | This hook is overwritten by modules such as C<Coro::Timer> and |
135 | This hook is overwritten by modules such as C<Coro::EV> and |
119 | C<Coro::AnyEvent> to wait on an external event that hopefully wake up a |
136 | C<Coro::AnyEvent> to wait on an external event that hopefully wake up a |
120 | coroutine so the scheduler can run it. |
137 | coroutine so the scheduler can run it. |
121 | |
138 | |
122 | Note that the callback I<must not>, under any circumstances, block |
139 | Note that the callback I<must not>, under any circumstances, block |
123 | the current coroutine. Normally, this is achieved by having an "idle |
140 | the current coroutine. Normally, this is achieved by having an "idle |
124 | coroutine" that calls the event loop and then blocks again, and then |
141 | coroutine" that calls the event loop and then blocks again, and then |
125 | readying that coroutine in the idle handler. |
142 | readying that coroutine in the idle handler, or by simply placing the idle |
|
|
143 | coroutine in this variable. |
126 | |
144 | |
127 | See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this |
145 | See L<Coro::Event> or L<Coro::AnyEvent> for examples of using this |
128 | technique. |
146 | technique. |
129 | |
147 | |
130 | Please note that if your callback recursively invokes perl (e.g. for event |
148 | Please note that if your callback recursively invokes perl (e.g. for event |
… | |
… | |
153 | $manager->{desc} = "[coro manager]"; |
171 | $manager->{desc} = "[coro manager]"; |
154 | $manager->prio (PRIO_MAX); |
172 | $manager->prio (PRIO_MAX); |
155 | |
173 | |
156 | =back |
174 | =back |
157 | |
175 | |
158 | =head2 SIMPLE COROUTINE CREATION |
176 | =head1 SIMPLE COROUTINE CREATION |
159 | |
177 | |
160 | =over 4 |
178 | =over 4 |
161 | |
179 | |
162 | =item async { ... } [@args...] |
180 | =item async { ... } [@args...] |
163 | |
181 | |
164 | Create a new coroutine and return it's coroutine object (usually |
182 | Create a new coroutine and return its coroutine object (usually |
165 | unused). The coroutine will be put into the ready queue, so |
183 | unused). The coroutine will be put into the ready queue, so |
166 | it will start running automatically on the next scheduler run. |
184 | it will start running automatically on the next scheduler run. |
167 | |
185 | |
168 | The first argument is a codeblock/closure that should be executed in the |
186 | The first argument is a codeblock/closure that should be executed in the |
169 | coroutine. When it returns argument returns the coroutine is automatically |
187 | coroutine. When it returns argument returns the coroutine is automatically |
… | |
… | |
225 | coros as required. |
243 | coros as required. |
226 | |
244 | |
227 | If you are concerned about pooled coroutines growing a lot because a |
245 | If you are concerned about pooled coroutines growing a lot because a |
228 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
246 | single C<async_pool> used a lot of stackspace you can e.g. C<async_pool |
229 | { terminate }> once per second or so to slowly replenish the pool. In |
247 | { terminate }> once per second or so to slowly replenish the pool. In |
230 | addition to that, when the stacks used by a handler grows larger than 16kb |
248 | addition to that, when the stacks used by a handler grows larger than 32kb |
231 | (adjustable via $Coro::POOL_RSS) it will also be destroyed. |
249 | (adjustable via $Coro::POOL_RSS) it will also be destroyed. |
232 | |
250 | |
233 | =cut |
251 | =cut |
234 | |
252 | |
235 | our $POOL_SIZE = 8; |
253 | our $POOL_SIZE = 8; |
236 | our $POOL_RSS = 16 * 1024; |
254 | our $POOL_RSS = 32 * 1024; |
237 | our @async_pool; |
255 | our @async_pool; |
238 | |
256 | |
239 | sub pool_handler { |
257 | sub pool_handler { |
240 | while () { |
258 | while () { |
241 | eval { |
259 | eval { |
… | |
… | |
246 | } |
264 | } |
247 | } |
265 | } |
248 | |
266 | |
249 | =back |
267 | =back |
250 | |
268 | |
251 | =head2 STATIC METHODS |
269 | =head1 STATIC METHODS |
252 | |
270 | |
253 | Static methods are actually functions that operate on the current coroutine. |
271 | Static methods are actually functions that implicitly operate on the |
|
|
272 | current coroutine. |
254 | |
273 | |
255 | =over 4 |
274 | =over 4 |
256 | |
275 | |
257 | =item schedule |
276 | =item schedule |
258 | |
277 | |
… | |
… | |
295 | |
314 | |
296 | =item terminate [arg...] |
315 | =item terminate [arg...] |
297 | |
316 | |
298 | Terminates the current coroutine with the given status values (see L<cancel>). |
317 | Terminates the current coroutine with the given status values (see L<cancel>). |
299 | |
318 | |
|
|
319 | =item Coro::on_enter BLOCK, Coro::on_leave BLOCK |
|
|
320 | |
|
|
321 | These function install enter and leave winders in the current scope. The |
|
|
322 | enter block will be executed when on_enter is called and whenever the |
|
|
323 | current coroutine is re-entered by the scheduler, while the leave block is |
|
|
324 | executed whenever the current coroutine is blocked by the scheduler, and |
|
|
325 | also when the containing scope is exited (by whatever means, be it exit, |
|
|
326 | die, last etc.). |
|
|
327 | |
|
|
328 | I<Neither invoking the scheduler, nor exceptions, are allowed within those |
|
|
329 | BLOCKs>. That means: do not even think about calling C<die> without an |
|
|
330 | eval, and do not even think of entering the scheduler in any way. |
|
|
331 | |
|
|
332 | Since both BLOCKs are tied to the current scope, they will automatically |
|
|
333 | be removed when the current scope exits. |
|
|
334 | |
|
|
335 | These functions implement the same concept as C<dynamic-wind> in scheme |
|
|
336 | does, and are useful when you want to localise some resource to a specific |
|
|
337 | coroutine. |
|
|
338 | |
|
|
339 | They slow down coroutine switching considerably for coroutines that use |
|
|
340 | them (But coroutine switching is still reasonably fast if the handlers are |
|
|
341 | fast). |
|
|
342 | |
|
|
343 | These functions are best understood by an example: The following function |
|
|
344 | will change the current timezone to "Antarctica/South_Pole", which |
|
|
345 | requires a call to C<tzset>, but by using C<on_enter> and C<on_leave>, |
|
|
346 | which remember/change the current timezone and restore the previous |
|
|
347 | value, respectively, the timezone is only changes for the coroutine that |
|
|
348 | installed those handlers. |
|
|
349 | |
|
|
350 | use POSIX qw(tzset); |
|
|
351 | |
|
|
352 | async { |
|
|
353 | my $old_tz; # store outside TZ value here |
|
|
354 | |
|
|
355 | Coro::on_enter { |
|
|
356 | $old_tz = $ENV{TZ}; # remember the old value |
|
|
357 | |
|
|
358 | $ENV{TZ} = "Antarctica/South_Pole"; |
|
|
359 | tzset; # enable new value |
|
|
360 | }; |
|
|
361 | |
|
|
362 | Coro::on_leave { |
|
|
363 | $ENV{TZ} = $old_tz; |
|
|
364 | tzset; # restore old value |
|
|
365 | }; |
|
|
366 | |
|
|
367 | # at this place, the timezone is Antarctica/South_Pole, |
|
|
368 | # without disturbing the TZ of any other coroutine. |
|
|
369 | }; |
|
|
370 | |
|
|
371 | This can be used to localise about any resource (locale, uid, current |
|
|
372 | working directory etc.) to a block, despite the existance of other |
|
|
373 | coroutines. |
|
|
374 | |
300 | =item killall |
375 | =item killall |
301 | |
376 | |
302 | Kills/terminates/cancels all coroutines except the currently running |
377 | Kills/terminates/cancels all coroutines except the currently running one. |
303 | one. This is useful after a fork, either in the child or the parent, as |
|
|
304 | usually only one of them should inherit the running coroutines. |
|
|
305 | |
378 | |
306 | Note that while this will try to free some of the main programs resources, |
379 | Note that while this will try to free some of the main interpreter |
|
|
380 | resources if the calling coroutine isn't the main coroutine, but one |
307 | you cannot free all of them, so if a coroutine that is not the main |
381 | cannot free all of them, so if a coroutine that is not the main coroutine |
308 | program calls this function, there will be some one-time resource leak. |
382 | calls this function, there will be some one-time resource leak. |
309 | |
383 | |
310 | =cut |
384 | =cut |
311 | |
385 | |
312 | sub killall { |
386 | sub killall { |
313 | for (Coro::State::list) { |
387 | for (Coro::State::list) { |
… | |
… | |
316 | } |
390 | } |
317 | } |
391 | } |
318 | |
392 | |
319 | =back |
393 | =back |
320 | |
394 | |
321 | =head2 COROUTINE METHODS |
395 | =head1 COROUTINE OBJECT METHODS |
322 | |
396 | |
323 | These are the methods you can call on coroutine objects (or to create |
397 | These are the methods you can call on coroutine objects (or to create |
324 | them). |
398 | them). |
325 | |
399 | |
326 | =over 4 |
400 | =over 4 |
… | |
… | |
335 | See C<async> and C<Coro::State::new> for additional info about the |
409 | See C<async> and C<Coro::State::new> for additional info about the |
336 | coroutine environment. |
410 | coroutine environment. |
337 | |
411 | |
338 | =cut |
412 | =cut |
339 | |
413 | |
340 | sub _terminate { |
414 | sub _coro_run { |
341 | terminate &{+shift}; |
415 | terminate &{+shift}; |
342 | } |
416 | } |
343 | |
417 | |
344 | =item $success = $coroutine->ready |
418 | =item $success = $coroutine->ready |
345 | |
419 | |
… | |
… | |
498 | my $old = $_[0]{desc}; |
572 | my $old = $_[0]{desc}; |
499 | $_[0]{desc} = $_[1] if @_ > 1; |
573 | $_[0]{desc} = $_[1] if @_ > 1; |
500 | $old; |
574 | $old; |
501 | } |
575 | } |
502 | |
576 | |
|
|
577 | sub transfer { |
|
|
578 | require Carp; |
|
|
579 | Carp::croak ("You must not call ->transfer on Coro objects. Use Coro::State objects or the ->schedule_to method. Caught"); |
|
|
580 | } |
|
|
581 | |
503 | =back |
582 | =back |
504 | |
583 | |
505 | =head2 GLOBAL FUNCTIONS |
584 | =head1 GLOBAL FUNCTIONS |
506 | |
585 | |
507 | =over 4 |
586 | =over 4 |
508 | |
587 | |
509 | =item Coro::nready |
588 | =item Coro::nready |
510 | |
589 | |
… | |
… | |
515 | would cause a deadlock unless there is an idle handler that wakes up some |
594 | would cause a deadlock unless there is an idle handler that wakes up some |
516 | coroutines. |
595 | coroutines. |
517 | |
596 | |
518 | =item my $guard = Coro::guard { ... } |
597 | =item my $guard = Coro::guard { ... } |
519 | |
598 | |
520 | This creates and returns a guard object. Nothing happens until the object |
599 | This function still exists, but is deprecated. Please use the |
521 | gets destroyed, in which case the codeblock given as argument will be |
600 | C<Guard::guard> function instead. |
522 | executed. This is useful to free locks or other resources in case of a |
|
|
523 | runtime error or when the coroutine gets canceled, as in both cases the |
|
|
524 | guard block will be executed. The guard object supports only one method, |
|
|
525 | C<< ->cancel >>, which will keep the codeblock from being executed. |
|
|
526 | |
601 | |
527 | Example: set some flag and clear it again when the coroutine gets canceled |
|
|
528 | or the function returns: |
|
|
529 | |
|
|
530 | sub do_something { |
|
|
531 | my $guard = Coro::guard { $busy = 0 }; |
|
|
532 | $busy = 1; |
|
|
533 | |
|
|
534 | # do something that requires $busy to be true |
|
|
535 | } |
|
|
536 | |
|
|
537 | =cut |
602 | =cut |
538 | |
603 | |
539 | sub guard(&) { |
604 | BEGIN { *guard = \&Guard::guard } |
540 | bless \(my $cb = $_[0]), "Coro::guard" |
|
|
541 | } |
|
|
542 | |
|
|
543 | sub Coro::guard::cancel { |
|
|
544 | ${$_[0]} = sub { }; |
|
|
545 | } |
|
|
546 | |
|
|
547 | sub Coro::guard::DESTROY { |
|
|
548 | ${$_[0]}->(); |
|
|
549 | } |
|
|
550 | |
|
|
551 | |
605 | |
552 | =item unblock_sub { ... } |
606 | =item unblock_sub { ... } |
553 | |
607 | |
554 | This utility function takes a BLOCK or code reference and "unblocks" it, |
608 | This utility function takes a BLOCK or code reference and "unblocks" it, |
555 | returning a new coderef. Unblocking means that calling the new coderef |
609 | returning a new coderef. Unblocking means that calling the new coderef |
… | |
… | |
557 | original code ref will be called (with parameters) from within another |
611 | original code ref will be called (with parameters) from within another |
558 | coroutine. |
612 | coroutine. |
559 | |
613 | |
560 | The reason this function exists is that many event libraries (such as the |
614 | The reason this function exists is that many event libraries (such as the |
561 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
615 | venerable L<Event|Event> module) are not coroutine-safe (a weaker form |
562 | of thread-safety). This means you must not block within event callbacks, |
616 | of reentrancy). This means you must not block within event callbacks, |
563 | otherwise you might suffer from crashes or worse. The only event library |
617 | otherwise you might suffer from crashes or worse. The only event library |
564 | currently known that is safe to use without C<unblock_sub> is L<EV>. |
618 | currently known that is safe to use without C<unblock_sub> is L<EV>. |
565 | |
619 | |
566 | This function allows your callbacks to block by executing them in another |
620 | This function allows your callbacks to block by executing them in another |
567 | coroutine where it is safe to block. One example where blocking is handy |
621 | coroutine where it is safe to block. One example where blocking is handy |
… | |
… | |
613 | } |
667 | } |
614 | } |
668 | } |
615 | |
669 | |
616 | =item $cb = Coro::rouse_cb |
670 | =item $cb = Coro::rouse_cb |
617 | |
671 | |
618 | Create and return a "rouse callback". That's a code reference that, when |
672 | Create and return a "rouse callback". That's a code reference that, |
619 | called, will save its arguments and notify the owner coroutine of the |
673 | when called, will remember a copy of its arguments and notify the owner |
620 | callback. |
674 | coroutine of the callback. |
621 | |
675 | |
622 | See the next function. |
676 | See the next function. |
623 | |
677 | |
624 | =item @args = Coro::rouse_wait [$cb] |
678 | =item @args = Coro::rouse_wait [$cb] |
625 | |
679 | |
626 | Wait for the specified rouse callback (or the last one tht was created in |
680 | Wait for the specified rouse callback (or the last one that was created in |
627 | this coroutine). |
681 | this coroutine). |
628 | |
682 | |
629 | As soon as the callback is invoked (or when the calback was invoked before |
683 | As soon as the callback is invoked (or when the callback was invoked |
630 | C<rouse_wait>), it will return a copy of the arguments originally passed |
684 | before C<rouse_wait>), it will return the arguments originally passed to |
631 | to the rouse callback. |
685 | the rouse callback. |
632 | |
686 | |
633 | See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example. |
687 | See the section B<HOW TO WAIT FOR A CALLBACK> for an actual usage example. |
634 | |
688 | |
635 | =back |
689 | =back |
636 | |
690 | |
… | |
… | |
659 | |
713 | |
660 | Coro offers two functions specifically designed to make this easy, |
714 | Coro offers two functions specifically designed to make this easy, |
661 | C<Coro::rouse_cb> and C<Coro::rouse_wait>. |
715 | C<Coro::rouse_cb> and C<Coro::rouse_wait>. |
662 | |
716 | |
663 | The first function, C<rouse_cb>, generates and returns a callback that, |
717 | The first function, C<rouse_cb>, generates and returns a callback that, |
664 | when invoked, will save it's arguments and notify the coroutine that |
718 | when invoked, will save its arguments and notify the coroutine that |
665 | created the callback. |
719 | created the callback. |
666 | |
720 | |
667 | The second function, C<rouse_wait>, waits for the callback to be called |
721 | The second function, C<rouse_wait>, waits for the callback to be called |
668 | (by calling C<schedule> to go to sleep) and returns the arguments |
722 | (by calling C<schedule> to go to sleep) and returns the arguments |
669 | originally passed to the callback. |
723 | originally passed to the callback. |
… | |
… | |
716 | fix your libc and use a saner backend. |
770 | fix your libc and use a saner backend. |
717 | |
771 | |
718 | =item perl process emulation ("threads") |
772 | =item perl process emulation ("threads") |
719 | |
773 | |
720 | This module is not perl-pseudo-thread-safe. You should only ever use this |
774 | This module is not perl-pseudo-thread-safe. You should only ever use this |
721 | module from the same thread (this requirement might be removed in the |
775 | module from the first thread (this requirement might be removed in the |
722 | future to allow per-thread schedulers, but Coro::State does not yet allow |
776 | future to allow per-thread schedulers, but Coro::State does not yet allow |
723 | this). I recommend disabling thread support and using processes, as having |
777 | this). I recommend disabling thread support and using processes, as having |
724 | the windows process emulation enabled under unix roughly halves perl |
778 | the windows process emulation enabled under unix roughly halves perl |
725 | performance, even when not used. |
779 | performance, even when not used. |
726 | |
780 | |
… | |
… | |
743 | |
797 | |
744 | Debugging: L<Coro::Debug>. |
798 | Debugging: L<Coro::Debug>. |
745 | |
799 | |
746 | Support/Utility: L<Coro::Specific>, L<Coro::Util>. |
800 | Support/Utility: L<Coro::Specific>, L<Coro::Util>. |
747 | |
801 | |
748 | Locking/IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
802 | Locking and IPC: L<Coro::Signal>, L<Coro::Channel>, L<Coro::Semaphore>, |
|
|
803 | L<Coro::SemaphoreSet>, L<Coro::RWLock>. |
749 | |
804 | |
750 | IO/Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>. |
805 | I/O and Timers: L<Coro::Timer>, L<Coro::Handle>, L<Coro::Socket>, L<Coro::AIO>. |
751 | |
806 | |
752 | Compatibility: L<Coro::LWP>, L<Coro::BDB>, L<Coro::Storable>, L<Coro::Select>. |
807 | Compatibility with other modules: L<Coro::LWP> (but see also L<AnyEvent::HTTP> for |
|
|
808 | a better-working alternative), L<Coro::BDB>, L<Coro::Storable>, |
|
|
809 | L<Coro::Select>. |
753 | |
810 | |
754 | XS API: L<Coro::MakeMaker>. |
811 | XS API: L<Coro::MakeMaker>. |
755 | |
812 | |
756 | Low level Configuration, Coroutine Environment: L<Coro::State>. |
813 | Low level Configuration, Thread Environment, Continuations: L<Coro::State>. |
757 | |
814 | |
758 | =head1 AUTHOR |
815 | =head1 AUTHOR |
759 | |
816 | |
760 | Marc Lehmann <schmorp@schmorp.de> |
817 | Marc Lehmann <schmorp@schmorp.de> |
761 | http://home.schmorp.de/ |
818 | http://home.schmorp.de/ |