| … | |
… | |
| 37 | 1; |
37 | 1; |
| 38 | __END__ |
38 | __END__ |
| 39 | |
39 | |
| 40 | =head1 NAME |
40 | =head1 NAME |
| 41 | |
41 | |
| 42 | Coro::MakeMaker - MakeMaker glue for the C-level Coro API |
42 | Coro::MakeMaker - MakeMaker glue for the XS-level Coro API |
| 43 | |
43 | |
| 44 | =head1 SYNOPSIS |
44 | =head1 SYNOPSIS |
| 45 | |
45 | |
| 46 | This allows you to control coroutines from C level. |
46 | This allows you to control coroutines from C/XS. |
| 47 | |
47 | |
| 48 | =head1 DESCRIPTION |
48 | =head1 DESCRIPTION |
| 49 | |
49 | |
| 50 | For optimal performance, hook into Coro at the C-level. You'll need |
50 | For optimal performance, hook into Coro at the C-level. You'll need to |
| 51 | to make changes to your C<Makefile.PL> and add code to your C<xs> / |
51 | make changes to your C<Makefile.PL> and add code to your C<xs> / C<c> |
| 52 | C<c> file(s). |
52 | file(s). |
| 53 | |
53 | |
| 54 | =head1 WARNING |
54 | =head1 WARNING |
| 55 | |
55 | |
| 56 | When you hook in at the C-level you get a I<huge> performance gain, |
56 | When you hook in at the C-level you can get a I<huge> performance gain, |
| 57 | but you also reduce the chances that your code will work unmodified |
57 | but you also reduce the chances that your code will work unmodified with |
| 58 | with newer versions of C<perl> or C<Coro>. This may or may not be a |
58 | newer versions of C<perl> or C<Coro>. This may or may not be a problem. |
| 59 | problem. Just be aware, and set your expectations accordingly. |
59 | Just be aware, and set your expectations accordingly. |
| 60 | |
60 | |
| 61 | =head1 HOW TO |
61 | =head1 HOW TO |
| 62 | |
62 | |
| 63 | =head2 Makefile.PL |
63 | =head2 Makefile.PL |
| 64 | |
64 | |
