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

Comparing Coro/Coro.pm (file contents):
Revision 1.6 by root, Tue Jul 10 21:19:47 2001 UTC vs.
Revision 1.14 by root, Tue Jul 17 02:21:56 2001 UTC

1=head1 NAME 1=head1 NAME
2 2
3Coro - create and manage simple coroutines 3Coro - coroutine process abstraction
4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 use Coro; 7 use Coro;
8 8
9 $new = new Coro sub { 9 async {
10 print "in coroutine, switching back\n"; 10 # some asynchronous thread of execution
11 $new->transfer($main);
12 print "in coroutine again, switching back\n";
13 $new->transfer($main);
14 }; 11 };
15 12
16 $main = new Coro; 13 # alternatively create an async process like this:
17 14
18 print "in main, switching to coroutine\n"; 15 sub some_func : Coro {
19 $main->transfer($new); 16 # some more async code
20 print "back in main, switch to coroutine again\n"; 17 }
21 $main->transfer($new); 18
22 print "back in main\n"; 19 yield;
23 20
24=head1 DESCRIPTION 21=head1 DESCRIPTION
25 22
26This module implements coroutines. Coroutines, similar to continuations, 23This module collection manages coroutines. Coroutines are similar to
27allow you to run more than one "thread of execution" in parallel. Unlike 24Threads but don't run in parallel.
28threads this, only voluntary switching is used so locking problems are
29greatly reduced.
30 25
31Although this is the "main" module of the Coro family it provides only 26This module is still experimental, see the BUGS section below.
32low-level functionality. See L<Coro::Process> and related modules for a 27
33more useful process abstraction including scheduling. 28=cut
29
30package Coro;
31
32use Coro::State;
33
34use base Exporter;
35
36$VERSION = 0.05;
37
38@EXPORT = qw(async yield schedule terminate);
39@EXPORT_OK = qw($current);
40
41{
42 use subs 'async';
43
44 my @async;
45
46 # this way of handling attributes simply is NOT scalable ;()
47 sub import {
48 Coro->export_to_level(1, @_);
49 my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
50 *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {
51 my ($package, $ref) = (shift, shift);
52 my @attrs;
53 for (@_) {
54 if ($_ eq "Coro") {
55 push @async, $ref;
56 } else {
57 push @attrs, @_;
58 }
59 }
60 return $old ? $old->($package, $name, @attrs) : @attrs;
61 };
62 }
63
64 sub INIT {
65 async pop @async while @async;
66 }
67}
68
69=item $main
70
71This coroutine represents the main program.
72
73=cut
74
75our $main = new Coro;
76
77=item $current
78
79The current coroutine (the last coroutine switched to). The initial value is C<$main> (of course).
80
81=cut
82
83# maybe some other module used Coro::Specific before...
84if ($current) {
85 $main->{specific} = $current->{specific};
86}
87
88our $current = $main;
89
90=item $idle
91
92The coroutine to switch to when no other coroutine is running. The default
93implementation prints "FATAL: deadlock detected" and exits.
94
95=cut
96
97# should be done using priorities :(
98our $idle = new Coro sub {
99 print STDERR "FATAL: deadlock detected\n";
100 exit(51);
101};
102
103# we really need priorities...
104## my @ready; #d#
105our @ready = (); # the ready queue. hehe, rather broken ;)
106
107# static methods. not really.
108
109=head2 STATIC METHODS
110
111Static methods are actually functions that operate on the current process only.
34 112
35=over 4 113=over 4
36 114
37=cut 115=item async { ... } [@args...]
38 116
39package Coro; 117Create a new asynchronous process and return it's process object
118(usually unused). When the sub returns the new process is automatically
119terminated.
40 120
41BEGIN { 121 # create a new coroutine that just prints its arguments
42 $VERSION = 0.03; 122 async {
123 print "@_\n";
124 } 1,2,3,4;
43 125
44 require XSLoader; 126The coderef you submit MUST NOT be a closure that refers to variables
45 XSLoader::load Coro, $VERSION; 127in an outer scope. This does NOT work. Pass arguments into it instead.
46}
47 128
48=item $coro = new [$coderef [, @args]]
49
50Create a new coroutine and return it. The first C<transfer> call to this
51coroutine will start execution at the given coderef. If, the subroutine
52returns it will be executed again.
53
54If the coderef is omitted this function will create a new "empty"
55coroutine, i.e. a coroutine that cannot be transfered to but can be used
56to save the current coroutine in.
57
58=cut 129=cut
130
131sub async(&@) {
132 my $pid = new Coro @_;
133 $pid->ready;
134 $pid;
135}
136
137=item schedule
138
139Calls the scheduler. Please note that the current process will not be put
140into the ready queue, so calling this function usually means you will
141never be called again.
142
143=cut
144
145my $prev;
146
147sub schedule {
148 # should be done using priorities :(
149 ($prev, $current) = ($current, shift @ready || $idle);
150 Coro::State::transfer($prev, $current);
151}
152
153=item yield
154
155Yield to other processes. This function puts the current process into the
156ready queue and calls C<schedule>.
157
158=cut
159
160sub yield {
161 $current->ready;
162 &schedule;
163}
164
165=item terminate
166
167Terminates the current process.
168
169Future versions of this function will allow result arguments.
170
171=cut
172
173sub terminate {
174 $current->{_results} = [@_];
175 &schedule;
176}
177
178=back
179
180# dynamic methods
181
182=head2 PROCESS METHODS
183
184These are the methods you can call on process objects.
185
186=over 4
187
188=item new Coro \&sub [, @args...]
189
190Create a new process and return it. When the sub returns the process
191automatically terminates. To start the process you must first put it into
192the ready queue by calling the ready method.
193
194The coderef you submit MUST NOT be a closure that refers to variables
195in an outer scope. This does NOT work. Pass arguments into it instead.
196
197=cut
198
199sub _newcoro {
200 terminate &{+shift};
201}
59 202
60sub new { 203sub new {
61 my $class = $_[0]; 204 my $class = shift;
62 my $proc = $_[1] || sub { die "tried to transfer to an empty coroutine" }; 205 bless {
63 bless _newprocess { 206 _coro_state => (new Coro::State $_[0] && \&_newcoro, @_),
64 do {
65 eval { &$proc };
66 if ($@) {
67 $error_msg = $@;
68 $error_coro = _newprocess { };
69 &transfer($error_coro, $error);
70 }
71 } while (1);
72 }, $class; 207 }, $class;
73} 208}
74 209
75=item $prev->transfer($next) 210=item $process->ready
76 211
77Save the state of the current subroutine in $prev and switch to the 212Put the current process into the ready queue.
78coroutine saved in $next.
79 213
80=cut 214=cut
81 215
82# I call the _transfer function from a perl function 216sub ready {
83# because that way perl saves all important things on 217 push @ready, $_[0];
84# the stack.
85sub transfer {
86 _transfer($_[0], $_[1]);
87} 218}
88 219
89=item $error, $error_msg, $error_coro 220=back
90 221
91This coroutine will be called on fatal errors. C<$error_msg> and
92C<$error_coro> return the error message and the error-causing coroutine
93(NOT an object) respectively. This API might change.
94
95=cut 222=cut
96
97$error_msg =
98$error_coro = undef;
99
100$error = _newprocess {
101 print STDERR "FATAL: $error_msg\nprogram aborted\n";
102 exit 50;
103};
104 223
1051; 2241;
106 225
107=back
108
109=head1 BUGS 226=head1 BUGS
110 227
111This module has not yet been extensively tested. 228 - could be faster, especially when the core would introduce special
229 support for coroutines (like it does for threads).
230 - there is still a memleak on coroutine termination that I could not
231 identify. Could be as small as a single SV.
232 - this module is not well-tested.
112 233
113=head1 SEE ALSO 234=head1 SEE ALSO
114 235
115L<Coro::Process>, L<Coro::Signal>. 236L<Coro::Channel>, L<Coro::Cont>, L<Coro::Specific>, L<Coro::Semaphore>,
237L<Coro::Signal>, L<Coro::State>, L<Coro::Event>.
116 238
117=head1 AUTHOR 239=head1 AUTHOR
118 240
119 Marc Lehmann <pcg@goof.com> 241 Marc Lehmann <pcg@goof.com>
120 http://www.goof.com/pcg/marc/ 242 http://www.goof.com/pcg/marc/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines