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

Comparing EV/EV.pm (file contents):
Revision 1.108 by root, Mon Nov 3 12:13:15 2008 UTC vs.
Revision 1.118 by root, Tue Jul 14 20:31:21 2009 UTC

… …
76 76
77=cut 77=cut
78 78
79package EV; 79package EV;
80 80
81no warnings; 81use common::sense;
82use strict;
83 82
84BEGIN { 83BEGIN {
85 our $VERSION = '3.48'; 84 our $VERSION = '3.7';
86 use XSLoader; 85 use XSLoader;
87 XSLoader::load "EV", $VERSION; 86 XSLoader::load "EV", $VERSION;
88} 87}
89 88
90@EV::IO::ISA = 89@EV::IO::ISA =
… …
125will then also service the kqueue loop to some extent. See the example in 124will then also service the kqueue loop to some extent. See the example in
126the section about embed watchers for an example on how to achieve that. 125the section about embed watchers for an example on how to achieve that.
127 126
128=over 4 127=over 4
129 128
130=item $loop = new EV::loop [$flags] 129=item $loop = new EV::Loop [$flags]
131 130
132Create a new event loop as per the specified flags. Please refer to 131Create a new event loop as per the specified flags. Please refer to
133the C<ev_loop_new ()> function description in the libev documentation 132the C<ev_loop_new ()> function description in the libev documentation
134(L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>, 133(L<http://pod.tst.eu/http://cvs.schmorp.de/libev/ev.pod#GLOBAL_FUNCTIONS>,
135or locally-installed as F<EV::libev> manpage) for more info. 134or locally-installed as F<EV::libev> manpage) for more info.
… …
201=item $time = $loop->now 200=item $time = $loop->now
202 201
203Returns the time the last event loop iteration has been started. This 202Returns the time the last event loop iteration has been started. This
204is the time that (relative) timers are based on, and referring to it is 203is the time that (relative) timers are based on, and referring to it is
205usually faster then calling EV::time. 204usually faster then calling EV::time.
205
206=item EV::now_update
207
208=item $loop->now_update
209
210Establishes the current time by querying the kernel, updating the time
211returned by C<EV::now> in the progress. This is a costly operation and
212is usually done automatically within C<EV::loop>.
213
214This function is rarely useful, but when some event callback runs for a
215very long time without entering the event loop, updating libev's idea of
216the current time is a good idea.
217
218=item EV::suspend
219
220=item $loop->suspend
221
222=item EV::resume
223
224=item $loop->resume
225
226These two functions suspend and resume a loop, for use when the loop is
227not used for a while and timeouts should not be processed.
228
229A typical use case would be an interactive program such as a game: When
230the user presses C<^Z> to suspend the game and resumes it an hour later it
231would be best to handle timeouts as if no time had actually passed while
232the program was suspended. This can be achieved by calling C<suspend>
233in your C<SIGTSTP> handler, sending yourself a C<SIGSTOP> and calling
234C<resume> directly afterwards to resume timer processing.
235
236Effectively, all C<timer> watchers will be delayed by the time spend
237between C<suspend> and C<resume>, and all C<periodic> watchers
238will be rescheduled (that is, they will lose any events that would have
239occured while suspended).
240
241After calling C<suspend> you B<must not> call I<any> function on the given
242loop other than C<resume>, and you B<must not> call C<resume>
243without a previous call to C<suspend>.
244
245Calling C<suspend>/C<resume> has the side effect of updating the event
246loop time (see C<now_update>).
206 247
207=item $backend = EV::backend 248=item $backend = EV::backend
208 249
209=item $backend = $loop->backend 250=item $backend = $loop->backend
210 251
… …
1002 1043
1003=back 1044=back
1004 1045
1005=head3 ASYNC WATCHERS - how to wake up another event loop 1046=head3 ASYNC WATCHERS - how to wake up another event loop
1006 1047
1007Async watchers are provided by EV, but have little use in perl directly, as perl 1048Async watchers are provided by EV, but have little use in perl directly,
1008neither supports threads nor direct access to signal handlers or other 1049as perl neither supports threads running in parallel nor direct access to
1009contexts where they could be of value. 1050signal handlers or other contexts where they could be of value.
1010 1051
1011It is, however, possible to use them from the XS level. 1052It is, however, possible to use them from the XS level.
1012 1053
1013Please see the libev documentation for further details. 1054Please see the libev documentation for further details.
1014 1055
… …
1042 my $async_check = EV::check sub { }; 1083 my $async_check = EV::check sub { };
1043 1084
1044This ensures that perl gets into control for a short time to handle any 1085This ensures that perl gets into control for a short time to handle any
1045pending signals, and also ensures (slightly) slower overall operation. 1086pending signals, and also ensures (slightly) slower overall operation.
1046 1087
1047=head1 THREADS 1088=head1 ITHREADS
1048 1089
1049Threads are not supported by this module in any way. Perl pseudo-threads 1090Ithreads are not supported by this module in any way. Perl pseudo-threads
1050is evil stuff and must die. As soon as Perl gains real threads I will work 1091is evil stuff and must die. Real threads as provided by Coro are fully
1051on thread support for it. 1092supported (and enhanced support is available via L<Coro::EV>).
1052 1093
1053=head1 FORK 1094=head1 FORK
1054 1095
1055Most of the "improved" event delivering mechanisms of modern operating 1096Most of the "improved" event delivering mechanisms of modern operating
1056systems have quite a few problems with fork(2) (to put it bluntly: it is 1097systems have quite a few problems with fork(2) (to put it bluntly: it is

Diff Legend

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