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

Comparing Coro/Coro.pm (file contents):
Revision 1.1 by root, Tue Jul 3 02:53:34 2001 UTC vs.
Revision 1.30 by root, Sat Aug 11 19:59:19 2001 UTC

1=head1 NAME 1=head1 NAME
2 2
3Coro - create an manage coroutines 3Coro - coroutine process abstraction
4 4
5=head1 SYNOPSIS 5=head1 SYNOPSIS
6 6
7 use Coro; 7 use Coro;
8 8
9 async {
10 # some asynchronous thread of execution
11 };
12
13 # alternatively create an async process like this:
14
15 sub some_func : Coro {
16 # some more async code
17 }
18
19 cede;
20
9=head1 DESCRIPTION 21=head1 DESCRIPTION
10 22
23This module collection manages coroutines. Coroutines are similar to
24Threads but don't run in parallel.
25
26This module is still experimental, see the BUGS section below.
27
28In this module, coroutines are defined as "callchain + lexical variables
29+ @_ + $_ + $@ + $^W + C stack), that is, a coroutine has it's own
30callchain, it's own set of lexicals and it's own set of perl's most
31important global variables.
32
33=cut
34
35package Coro;
36
37use Coro::State;
38
39use base Exporter;
40
41$VERSION = 0.45;
42
43@EXPORT = qw(async cede schedule terminate current);
44@EXPORT_OK = qw($current);
45
46{
47 my @async;
48 my $init;
49
50 # this way of handling attributes simply is NOT scalable ;()
51 sub import {
52 Coro->export_to_level(1, @_);
53 my $old = *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"}{CODE};
54 *{(caller)[0]."::MODIFY_CODE_ATTRIBUTES"} = sub {
55 my ($package, $ref) = (shift, shift);
56 my @attrs;
57 for (@_) {
58 if ($_ eq "Coro") {
59 push @async, $ref;
60 unless ($init++) {
61 eval q{
62 sub INIT {
63 &async(pop @async) while @async;
64 }
65 };
66 }
67 } else {
68 push @attrs, $_;
69 }
70 }
71 return $old ? $old->($package, $ref, @attrs) : @attrs;
72 };
73 }
74
75}
76
77=item $main
78
79This coroutine represents the main program.
80
81=cut
82
83our $main = new Coro;
84
85=item $current (or as function: current)
86
87The current coroutine (the last coroutine switched to). The initial value is C<$main> (of course).
88
89=cut
90
91# maybe some other module used Coro::Specific before...
92if ($current) {
93 $main->{specific} = $current->{specific};
94}
95
96our $current = $main;
97
98sub current() { $current }
99
100=item $idle
101
102The coroutine to switch to when no other coroutine is running. The default
103implementation prints "FATAL: deadlock detected" and exits.
104
105=cut
106
107# should be done using priorities :(
108our $idle = new Coro sub {
109 print STDERR "FATAL: deadlock detected\n";
110 exit(51);
111};
112
113# this coroutine is necessary because a coroutine
114# cannot destroy itself.
115my @destroy;
116my $manager = new Coro sub {
117 while() {
118 delete ((pop @destroy)->{_coro_state}) while @destroy;
119 &schedule;
120 }
121};
122
123# static methods. not really.
124
125=head2 STATIC METHODS
126
127Static methods are actually functions that operate on the current process only.
128
11=over 4 129=over 4
12 130
13=cut 131=item async { ... } [@args...]
14 132
15package Coro; 133Create a new asynchronous process and return it's process object
134(usually unused). When the sub returns the new process is automatically
135terminated.
16 136
17BEGIN { 137 # create a new coroutine that just prints its arguments
18 $VERSION = 0.01; 138 async {
139 print "@_\n";
140 } 1,2,3,4;
19 141
20 require XSLoader; 142The coderef you submit MUST NOT be a closure that refers to variables
21 XSLoader::load Coro, $VERSION; 143in an outer scope. This does NOT work. Pass arguments into it instead.
22}
23 144
24=item $main
25
26This coroutine represents the main program.
27
28=item $current
29
30The current coroutine (the last coroutine switched to). The initial value is C<$main> (of course).
31
32=cut 145=cut
33 146
34$main = $current = _newprocess { 147sub async(&@) {
35 # never being called 148 my $pid = new Coro @_;
36}; 149 $manager->ready; # this ensures that the stack is cloned from the manager
150 $pid->ready;
151 $pid;
152}
37 153
38=item $error, $error_msg, $error_coro 154=item schedule
39 155
40This coroutine will be called on fatal errors. C<$error_msg> and 156Calls the scheduler. Please note that the current process will not be put
41C<$error_coro> return the error message and the error-causing coroutine, 157into the ready queue, so calling this function usually means you will
42respectively. 158never be called again.
43 159
44=cut 160=cut
45 161
46$error_msg = 162=item cede
47$error_coro = undef;
48 163
49$error = _newprocess { 164"Cede" to other processes. This function puts the current process into the
50 print STDERR "FATAL: $error_msg, program aborted\n"; 165ready queue and calls C<schedule>, which has the effect of giving up the
51 exit 250; 166current "timeslice" to other coroutines of the same or higher priority.
52};
53 167
54=item $coro = new $coderef [, @args]
55
56Create a new coroutine and return it. The first C<resume> call to this
57coroutine will start execution at the given coderef. If it returns it
58should return a coroutine to switch to. If, after returning, the coroutine
59is C<resume>d again it starts execution again at the givne coderef.
60
61=cut 168=cut
169
170=item terminate
171
172Terminates the current process.
173
174Future versions of this function will allow result arguments.
175
176=cut
177
178sub terminate {
179 $current->cancel;
180 &schedule;
181 die; # NORETURN
182}
183
184=back
185
186# dynamic methods
187
188=head2 PROCESS METHODS
189
190These are the methods you can call on process objects.
191
192=over 4
193
194=item new Coro \&sub [, @args...]
195
196Create a new process and return it. When the sub returns the process
197automatically terminates. To start the process you must first put it into
198the ready queue by calling the ready method.
199
200The coderef you submit MUST NOT be a closure that refers to variables
201in an outer scope. This does NOT work. Pass arguments into it instead.
202
203=cut
204
205sub _newcoro {
206 terminate &{+shift};
207}
62 208
63sub new { 209sub new {
64 my $class = $_[0]; 210 my $class = shift;
65 my $proc = $_[1]; 211 bless {
66 bless _newprocess { 212 _coro_state => (new Coro::State $_[0] && \&_newcoro, @_),
67 do {
68 eval { &$proc->resume };
69 if ($@) {
70 ($error_msg, $error_coro) = ($@, $current);
71 $error->resume;
72 }
73 } while ();
74 }, $class; 213 }, $class;
75} 214}
76 215
77=item $coro->resume 216=item $process->ready
78 217
79Resume execution at the given coroutine. 218Put the current process into the ready queue.
80 219
81=cut 220=cut
82 221
83my $prev; 222=item $process->cancel
84 223
85sub resume { 224Like C<terminate>, but terminates the specified process instead.
86 $prev = $current; $current = $_[0]; 225
87 _transfer($prev, $current); 226=cut
227
228sub cancel {
229 push @destroy, $_[0];
230 $manager->ready;
88} 231}
232
233=back
234
235=cut
89 236
901; 2371;
91 238
92=back 239=head1 BUGS/LIMITATIONS
93 240
94=head1 BUGS 241 - could be faster, especially when the core would introduce special
242 support for coroutines (like it does for threads).
243 - there is still a memleak on coroutine termination that I could not
244 identify. Could be as small as a single SV.
245 - this module is not well-tested.
246 - if variables or arguments "disappear" (become undef) or become
247 corrupted please contact the author so he cen iron out the
248 remaining bugs.
249 - this module is not thread-safe. You must only ever use this module from
250 the same thread (this requirement might be loosened in the future to
251 allow per-thread schedulers, but Coro::State does not yet allow this).
95 252
96This module has not yet been extensively tested. 253=head1 SEE ALSO
254
255L<Coro::Channel>, L<Coro::Cont>, L<Coro::Specific>, L<Coro::Semaphore>,
256L<Coro::Signal>, L<Coro::State>, L<Coro::Event>, L<Coro::RWLock>,
257L<Coro::Handle>, L<Coro::Socket>.
97 258
98=head1 AUTHOR 259=head1 AUTHOR
99 260
100 Marc Lehmann <pcg@goof.com> 261 Marc Lehmann <pcg@goof.com>
101 http://www.goof.com/pcg/marc/ 262 http://www.goof.com/pcg/marc/

Diff Legend

Removed lines
+ Added lines
< Changed lines
> Changed lines