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

Comparing Coro/Event/Event.pm (file contents):
Revision 1.8 by root, Sun Oct 28 17:00:09 2001 UTC vs.
Revision 1.44 by root, Fri Dec 1 20:49:54 2006 UTC

… …
6 6
7 use Coro; 7 use Coro;
8 use Coro::Event; 8 use Coro::Event;
9 9
10 sub keyboard : Coro { 10 sub keyboard : Coro {
11 my $w = Coro::Event->io(fd => *STDIN, poll => 'r'); 11 my $w = Coro::Event->io(fd => \*STDIN, poll => 'r');
12 while() { 12 while() {
13 print "cmd> "; 13 print "cmd> ";
14 my $ev = $w->next; my $cmd = <STDIN>; 14 my $ev = $w->next; my $cmd = <STDIN>;
15 unloop unless $cmd ne ""; 15 unloop unless $cmd ne "";
16 print "data> "; 16 print "data> ";
… …
30(I<flavour>) (see L<Event>). The only difference between these and the 30(I<flavour>) (see L<Event>). The only difference between these and the
31watcher constructors from Event is that you do not specify a callback 31watcher constructors from Event is that you do not specify a callback
32function - it will be managed by this module. 32function - it will be managed by this module.
33 33
34Your application should just create all necessary coroutines and then call 34Your application should just create all necessary coroutines and then call
35Coro::Event->main. 35Coro::Event::loop.
36
37Please note that even programs or modules (such as
38L<Coro::Handle|Coro::Handle>) that use "traditional"
39event-based/continuation style will run more efficient with this module
40then when using only Event.
41
42=head1 WARNING
43
44Please note that Event does not support coroutines or threads. That
45means that you B<MUST NOT> block in an event callback. Again: In Event
46callbacks, you I<must never ever> call a Coroutine fucntion that blocks
47the current coroutine.
48
49While this seems to work superficially, it will eventually cause memory
50corruption.
51
52=head1 FUNCTIONS
36 53
37=over 4 54=over 4
38 55
39=cut 56=cut
40 57
41package Coro::Event; 58package Coro::Event;
42 59
43no warnings qw(uninitialized); 60no warnings;
44 61
45use Carp; 62use Carp;
63no warnings;
46 64
47use Coro; 65use Coro;
66use Coro::Timer;
48use Event qw(loop unloop); # we are re-exporting this, cooool! 67use Event qw(loop unloop); # we are re-exporting this, cooool!
49 68
50use base 'Exporter'; 69use XSLoader;
51 70
71use base Exporter::;
72
52@EXPORT = qw(loop unloop sweep reschedule); 73our @EXPORT = qw(loop unloop sweep);
53 74
54BEGIN { 75BEGIN {
55 $VERSION = 0.45; 76 our $VERSION = 1.9;
56 77
57 local $^W = 0; # avoid redefine warning for Coro::ready 78 local $^W = 0; # avoid redefine warning for Coro::ready;
58 require XSLoader;
59 XSLoader::load Coro::Event, $VERSION; 79 XSLoader::load __PACKAGE__, $VERSION;
60} 80}
61 81
62=item $w = Coro::Event->flavour(args...) 82=item $w = Coro::Event->flavour (args...)
63 83
64Create and return a watcher of the given type. 84Create and return a watcher of the given type.
65 85
66Examples: 86Examples:
67 87
… …
74 94
75Return the next event of the event queue of the watcher. 95Return the next event of the event queue of the watcher.
76 96
77=cut 97=cut
78 98
79=item do_flavour(args...) 99=item do_flavour args...
80 100
81Create a watcher of the given type and immediately call it's next 101Create a watcher of the given type and immediately call it's next
82method. This is less efficient then calling the constructor once and the 102method. This is less efficient then calling the constructor once and the
83next method often, but it does save typing sometimes. 103next method often, but it does save typing sometimes.
84 104
… …
92 @{"${class}::ISA"} = (Coro::Event::, "Event::$flavour"); 112 @{"${class}::ISA"} = (Coro::Event::, "Event::$flavour");
93 my $coronew = sub { 113 my $coronew = sub {
94 # how does one do method-call-by-name? 114 # how does one do method-call-by-name?
95 # my $w = $class->SUPER::$flavour(@_); 115 # my $w = $class->SUPER::$flavour(@_);
96 116
97 $_[0] eq Coro::Event:: 117 shift eq Coro::Event::
98 or croak "event constructor \"Coro::Event->$flavour\" must be called as a static method"; 118 or croak "event constructor \"Coro::Event->$flavour\" must be called as a static method";
99 119
100 my $q = []; # [$coro, $event]
101 my $w = $new->( 120 my $w = $new->($class,
102 desc => $flavour, 121 desc => $flavour,
103 @_, 122 @_,
104 parked => 1, 123 parked => 1,
105 ); 124 );
125
106 _install_std_cb($w, $type); 126 _install_std_cb $w, $type;
107 bless $w, $class; # reblessing due to broken Event 127
128 # reblessing due to Event being broken
129 bless $w, $class
108 }; 130 };
109 *{ $flavour } = $coronew; 131 *{ $flavour } = $coronew;
110 *{"do_$flavour"} = sub { 132 *{"do_$flavour"} = sub {
111 unshift @_, Coro::Event::; 133 unshift @_, Coro::Event::;
112 my $e = (&$coronew)->next; 134 @_ = &$coronew;
113 $e->cancel; # $e = $e->w->cancel ($e == $e->w!) 135 &Coro::schedule while &_next;
114 $e; 136 $_[0]->cancel;
137 &_event
115 }; 138 };
116} 139}
117 140
118# double calls to avoid stack-cloning ;() 141# do schedule in perl to avoid forcing a stack allocation.
119# is about 10% slower, though. 142# this is about 10% slower, though.
120sub next($) { 143sub next($) {
121 &Coro::schedule if &_next; $_[0]; 144 &Coro::schedule while &_next;
145
146 &_event
122} 147}
123 148
124sub Coro::Event::w { $_[0] } 149sub Coro::Event::w { $_[0] }
125sub Coro::Event::prio { $_[0]{Coro::Event}[3] } 150sub Coro::Event::prio { $_[0]{Coro::Event}[3] }
126sub Coro::Event::hits { $_[0]{Coro::Event}[4] } 151sub Coro::Event::hits { $_[0]{Coro::Event}[4] }
… …
138into the Event dispatcher. 163into the Event dispatcher.
139 164
140=cut 165=cut
141 166
142sub sweep { 167sub sweep {
143 Event::one_event(0); # for now 168 Event::one_event 0; # for now
144} 169}
145 170
146=item $result = loop([$timeout]) 171=item $result = loop([$timeout])
147 172
148This is the version of C<loop> you should use instead of C<Event::loop> 173This is the version of C<loop> you should use instead of C<Event::loop>
149when using this module - it will ensure correct scheduling in the presence 174when using this module - it will ensure correct scheduling in the presence
150of events. 175of events.
151 176
152=begin comment
153
154Unlike loop's counterpart it is not an error when no watchers are active -
155loop silently returns in this case, as if unloop(undef) were called.
156
157=end comment
158
159=cut
160
161# no longer do something special - it's done internally now
162
163#sub loop(;$) {
164# #local $Coro::idle = $Coro::current;
165# #Coro::schedule; # become idle task, which is implicitly ready
166# &Event::loop;
167#}
168
169=item unloop([$result]) 177=item unloop([$result])
170 178
171Same as Event::unloop (provided here for your convinience only). 179Same as Event::unloop (provided here for your convinience only).
172 180
173=cut 181=cut
174 182
175$Coro::idle = new Coro sub { 183$Coro::idle = \&Event::one_event; # inefficient
176 while () {
177 Event::one_event; # inefficient
178 Coro::schedule;
179 }
180};
181 184
1821; 1851;
183 186
187=back
188
184=head1 AUTHOR 189=head1 AUTHOR
185 190
186 Marc Lehmann <pcg@goof.com> 191 Marc Lehmann <schmorp@schmorp.de>
187 http://www.goof.com/pcg/marc/ 192 http://home.schmorp.de/
188 193
189=cut 194=cut
190 195

Diff Legend

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