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