1 | =head1 NAME |
1 | =head1 NAME |
2 | |
2 | |
3 | AnyEvent - provide framework for multiple event loops |
3 | AnyEvent - provide framework for multiple event loops |
4 | |
4 | |
5 | Event, Coro, Glib, Tk, Perl - various supported event loops |
5 | EV, Event, Coro::EV, Coro::Event, Glib, Tk, Perl, Event::Lib, Qt - various supported event loops |
6 | |
6 | |
7 | =head1 SYNOPSIS |
7 | =head1 SYNOPSIS |
8 | |
8 | |
9 | use AnyEvent; |
9 | use AnyEvent; |
10 | |
10 | |
… | |
… | |
14 | |
14 | |
15 | my $w = AnyEvent->timer (after => $seconds, cb => sub { |
15 | my $w = AnyEvent->timer (after => $seconds, cb => sub { |
16 | ... |
16 | ... |
17 | }); |
17 | }); |
18 | |
18 | |
19 | my $w = AnyEvent->condvar; # stores wether a condition was flagged |
19 | my $w = AnyEvent->condvar; # stores whether a condition was flagged |
20 | $w->wait; # enters "main loop" till $condvar gets ->broadcast |
20 | $w->wait; # enters "main loop" till $condvar gets ->broadcast |
21 | $w->broadcast; # wake up current and all future wait's |
21 | $w->broadcast; # wake up current and all future wait's |
22 | |
22 | |
23 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
23 | =head1 WHY YOU SHOULD USE THIS MODULE (OR NOT) |
24 | |
24 | |
… | |
… | |
29 | policy> and AnyEvent is I<small and efficient>. |
29 | policy> and AnyEvent is I<small and efficient>. |
30 | |
30 | |
31 | First and foremost, I<AnyEvent is not an event model> itself, it only |
31 | First and foremost, I<AnyEvent is not an event model> itself, it only |
32 | interfaces to whatever event model the main program happens to use in a |
32 | interfaces to whatever event model the main program happens to use in a |
33 | pragmatic way. For event models and certain classes of immortals alike, |
33 | pragmatic way. For event models and certain classes of immortals alike, |
34 | the statement "there can only be one" is a bitter reality, and AnyEvent |
34 | the statement "there can only be one" is a bitter reality: In general, |
35 | helps hiding the differences. |
35 | only one event loop can be active at the same time in a process. AnyEvent |
|
|
36 | helps hiding the differences between those event loops. |
36 | |
37 | |
37 | The goal of AnyEvent is to offer module authors the ability to do event |
38 | The goal of AnyEvent is to offer module authors the ability to do event |
38 | programming (waiting for I/O or timer events) without subscribing to a |
39 | programming (waiting for I/O or timer events) without subscribing to a |
39 | religion, a way of living, and most importantly: without forcing your |
40 | religion, a way of living, and most importantly: without forcing your |
40 | module users into the same thing by forcing them to use the same event |
41 | module users into the same thing by forcing them to use the same event |
41 | model you use. |
42 | model you use. |
42 | |
43 | |
43 | For modules like POE or IO::Async (which is actually doing all I/O |
44 | For modules like POE or IO::Async (which is a total misnomer as it is |
44 | I<synchronously>...), using them in your module is like joining a |
45 | actually doing all I/O I<synchronously>...), using them in your module is |
45 | cult: After you joined, you are dependent on them and you cannot use |
46 | like joining a cult: After you joined, you are dependent on them and you |
46 | anything else, as it is simply incompatible to everything that isn't |
47 | cannot use anything else, as it is simply incompatible to everything that |
47 | itself. |
48 | isn't itself. What's worse, all the potential users of your module are |
|
|
49 | I<also> forced to use the same event loop you use. |
48 | |
50 | |
49 | AnyEvent + POE works fine. AnyEvent + Glib works fine. AnyEvent + Tk |
51 | AnyEvent is different: AnyEvent + POE works fine. AnyEvent + Glib works |
50 | works fine etc. etc. but none of these work together with the rest: POE |
52 | fine. AnyEvent + Tk works fine etc. etc. but none of these work together |
51 | + IO::Async? no go. Tk + Event? no go. If your module uses one of |
53 | with the rest: POE + IO::Async? no go. Tk + Event? no go. Again: if |
52 | those, every user of your module has to use it, too. If your module |
54 | your module uses one of those, every user of your module has to use it, |
53 | uses AnyEvent, it works transparently with all event models it supports |
55 | too. But if your module uses AnyEvent, it works transparently with all |
54 | (including stuff like POE and IO::Async). |
56 | event models it supports (including stuff like POE and IO::Async, as long |
|
|
57 | as those use one of the supported event loops. It is trivial to add new |
|
|
58 | event loops to AnyEvent, too, so it is future-proof). |
55 | |
59 | |
56 | In addition of being free of having to use I<the one and only true event |
60 | In addition to being free of having to use I<the one and only true event |
57 | model>, AnyEvent also is free of bloat and policy: with POE or similar |
61 | model>, AnyEvent also is free of bloat and policy: with POE or similar |
58 | modules, you get an enourmous amount of code and strict rules you have |
62 | modules, you get an enourmous amount of code and strict rules you have to |
59 | to follow. AnyEvent, on the other hand, is lean and to the point by only |
63 | follow. AnyEvent, on the other hand, is lean and up to the point, by only |
60 | offering the functionality that is useful, in as thin as a wrapper as |
64 | offering the functionality that is necessary, in as thin as a wrapper as |
61 | technically possible. |
65 | technically possible. |
62 | |
66 | |
63 | Of course, if you want lots of policy (this can arguably be somewhat |
67 | Of course, if you want lots of policy (this can arguably be somewhat |
64 | useful) and you want to force your users to use the one and only event |
68 | useful) and you want to force your users to use the one and only event |
65 | model, you should I<not> use this module. |
69 | model, you should I<not> use this module. |
… | |
… | |
70 | L<AnyEvent> provides an identical interface to multiple event loops. This |
74 | L<AnyEvent> provides an identical interface to multiple event loops. This |
71 | allows module authors to utilise an event loop without forcing module |
75 | allows module authors to utilise an event loop without forcing module |
72 | users to use the same event loop (as only a single event loop can coexist |
76 | users to use the same event loop (as only a single event loop can coexist |
73 | peacefully at any one time). |
77 | peacefully at any one time). |
74 | |
78 | |
75 | The interface itself is vaguely similar but not identical to the Event |
79 | The interface itself is vaguely similar, but not identical to the L<Event> |
76 | module. |
80 | module. |
77 | |
81 | |
78 | On the first call of any method, the module tries to detect the currently |
82 | During the first call of any watcher-creation method, the module tries |
79 | loaded event loop by probing wether any of the following modules is |
83 | to detect the currently loaded event loop by probing whether one of |
80 | loaded: L<Coro::Event>, L<Event>, L<Glib>, L<Tk>. The first one found is |
84 | the following modules is already loaded: L<Coro::EV>, L<Coro::Event>, |
|
|
85 | L<EV>, L<Event>, L<Glib>, L<Tk>, L<Event::Lib>, L<Qt>. The first one |
81 | used. If none is found, the module tries to load these modules in the |
86 | found is used. If none are found, the module tries to load these modules |
82 | order given. The first one that could be successfully loaded will be |
87 | (excluding Event::Lib and Qt) in the order given. The first one that can |
83 | used. If still none could be found, AnyEvent will fall back to a pure-perl |
88 | be successfully loaded will be used. If, after this, still none could be |
84 | event loop, which is also not very efficient. |
89 | found, AnyEvent will fall back to a pure-perl event loop, which is not |
|
|
90 | very efficient, but should work everywhere. |
85 | |
91 | |
86 | Because AnyEvent first checks for modules that are already loaded, loading |
92 | Because AnyEvent first checks for modules that are already loaded, loading |
87 | an Event model explicitly before first using AnyEvent will likely make |
93 | an event model explicitly before first using AnyEvent will likely make |
88 | that model the default. For example: |
94 | that model the default. For example: |
89 | |
95 | |
90 | use Tk; |
96 | use Tk; |
91 | use AnyEvent; |
97 | use AnyEvent; |
92 | |
98 | |
93 | # .. AnyEvent will likely default to Tk |
99 | # .. AnyEvent will likely default to Tk |
|
|
100 | |
|
|
101 | The I<likely> means that, if any module loads another event model and |
|
|
102 | starts using it, all bets are off. Maybe you should tell their authors to |
|
|
103 | use AnyEvent so their modules work together with others seamlessly... |
94 | |
104 | |
95 | The pure-perl implementation of AnyEvent is called |
105 | The pure-perl implementation of AnyEvent is called |
96 | C<AnyEvent::Impl::Perl>. Like other event modules you can load it |
106 | C<AnyEvent::Impl::Perl>. Like other event modules you can load it |
97 | explicitly. |
107 | explicitly. |
98 | |
108 | |
… | |
… | |
101 | AnyEvent has the central concept of a I<watcher>, which is an object that |
111 | AnyEvent has the central concept of a I<watcher>, which is an object that |
102 | stores relevant data for each kind of event you are waiting for, such as |
112 | stores relevant data for each kind of event you are waiting for, such as |
103 | the callback to call, the filehandle to watch, etc. |
113 | the callback to call, the filehandle to watch, etc. |
104 | |
114 | |
105 | These watchers are normal Perl objects with normal Perl lifetime. After |
115 | These watchers are normal Perl objects with normal Perl lifetime. After |
106 | creating a watcher it will immediately "watch" for events and invoke |
116 | creating a watcher it will immediately "watch" for events and invoke the |
|
|
117 | callback when the event occurs (of course, only when the event model |
|
|
118 | is in control). |
|
|
119 | |
107 | the callback. To disable the watcher you have to destroy it (e.g. by |
120 | To disable the watcher you have to destroy it (e.g. by setting the |
108 | setting the variable that stores it to C<undef> or otherwise deleting all |
121 | variable you store it in to C<undef> or otherwise deleting all references |
109 | references to it). |
122 | to it). |
110 | |
123 | |
111 | All watchers are created by calling a method on the C<AnyEvent> class. |
124 | All watchers are created by calling a method on the C<AnyEvent> class. |
112 | |
125 | |
|
|
126 | Many watchers either are used with "recursion" (repeating timers for |
|
|
127 | example), or need to refer to their watcher object in other ways. |
|
|
128 | |
|
|
129 | An any way to achieve that is this pattern: |
|
|
130 | |
|
|
131 | my $w; $w = AnyEvent->type (arg => value ..., cb => sub { |
|
|
132 | # you can use $w here, for example to undef it |
|
|
133 | undef $w; |
|
|
134 | }); |
|
|
135 | |
|
|
136 | Note that C<my $w; $w => combination. This is necessary because in Perl, |
|
|
137 | my variables are only visible after the statement in which they are |
|
|
138 | declared. |
|
|
139 | |
113 | =head2 IO WATCHERS |
140 | =head2 IO WATCHERS |
114 | |
141 | |
115 | You can create I/O watcher by calling the C<< AnyEvent->io >> method with |
142 | You can create an I/O watcher by calling the C<< AnyEvent->io >> method |
116 | the following mandatory arguments: |
143 | with the following mandatory key-value pairs as arguments: |
117 | |
144 | |
118 | C<fh> the Perl I<filehandle> (not filedescriptor) to watch for |
145 | C<fh> the Perl I<file handle> (I<not> file descriptor) to watch for |
119 | events. C<poll> must be a string that is either C<r> or C<w>, that creates |
146 | events. C<poll> must be a string that is either C<r> or C<w>, which |
120 | a watcher waiting for "r"eadable or "w"ritable events. C<cb> the callback |
147 | creates a watcher waiting for "r"eadable or "w"ritable events, |
121 | to invoke everytime the filehandle becomes ready. |
148 | respectively. C<cb> is the callback to invoke each time the file handle |
|
|
149 | becomes ready. |
122 | |
150 | |
123 | Only one io watcher per C<fh> and C<poll> combination is allowed (i.e. on |
151 | As long as the I/O watcher exists it will keep the file descriptor or a |
124 | a socket you can have one r + one w, not any more (limitation comes from |
152 | copy of it alive/open. |
125 | Tk - if you are sure you are not using Tk this limitation is gone). |
|
|
126 | |
153 | |
127 | Filehandles will be kept alive, so as long as the watcher exists, the |
154 | It is not allowed to close a file handle as long as any watcher is active |
128 | filehandle exists, too. |
155 | on the underlying file descriptor. |
|
|
156 | |
|
|
157 | Some event loops issue spurious readyness notifications, so you should |
|
|
158 | always use non-blocking calls when reading/writing from/to your file |
|
|
159 | handles. |
129 | |
160 | |
130 | Example: |
161 | Example: |
131 | |
162 | |
132 | # wait for readability of STDIN, then read a line and disable the watcher |
163 | # wait for readability of STDIN, then read a line and disable the watcher |
133 | my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { |
164 | my $w; $w = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { |
… | |
… | |
139 | =head2 TIME WATCHERS |
170 | =head2 TIME WATCHERS |
140 | |
171 | |
141 | You can create a time watcher by calling the C<< AnyEvent->timer >> |
172 | You can create a time watcher by calling the C<< AnyEvent->timer >> |
142 | method with the following mandatory arguments: |
173 | method with the following mandatory arguments: |
143 | |
174 | |
144 | C<after> after how many seconds (fractions are supported) should the timer |
175 | C<after> specifies after how many seconds (fractional values are |
145 | activate. C<cb> the callback to invoke. |
176 | supported) should the timer activate. C<cb> the callback to invoke in that |
|
|
177 | case. |
146 | |
178 | |
147 | The timer callback will be invoked at most once: if you want a repeating |
179 | The timer callback will be invoked at most once: if you want a repeating |
148 | timer you have to create a new watcher (this is a limitation by both Tk |
180 | timer you have to create a new watcher (this is a limitation by both Tk |
149 | and Glib). |
181 | and Glib). |
150 | |
182 | |
… | |
… | |
156 | }); |
188 | }); |
157 | |
189 | |
158 | # to cancel the timer: |
190 | # to cancel the timer: |
159 | undef $w; |
191 | undef $w; |
160 | |
192 | |
|
|
193 | Example 2: |
|
|
194 | |
|
|
195 | # fire an event after 0.5 seconds, then roughly every second |
|
|
196 | my $w; |
|
|
197 | |
|
|
198 | my $cb = sub { |
|
|
199 | # cancel the old timer while creating a new one |
|
|
200 | $w = AnyEvent->timer (after => 1, cb => $cb); |
|
|
201 | }; |
|
|
202 | |
|
|
203 | # start the "loop" by creating the first watcher |
|
|
204 | $w = AnyEvent->timer (after => 0.5, cb => $cb); |
|
|
205 | |
|
|
206 | =head3 TIMING ISSUES |
|
|
207 | |
|
|
208 | There are two ways to handle timers: based on real time (relative, "fire |
|
|
209 | in 10 seconds") and based on wallclock time (absolute, "fire at 12 |
|
|
210 | o'clock"). |
|
|
211 | |
|
|
212 | While most event loops expect timers to specified in a relative way, they |
|
|
213 | use absolute time internally. This makes a difference when your clock |
|
|
214 | "jumps", for example, when ntp decides to set your clock backwards from |
|
|
215 | the wrong date of 2014-01-01 to 2008-01-01, a watcher that is supposed to |
|
|
216 | fire "after" a second might actually take six years to finally fire. |
|
|
217 | |
|
|
218 | AnyEvent cannot compensate for this. The only event loop that is conscious |
|
|
219 | about these issues is L<EV>, which offers both relative (ev_timer, based |
|
|
220 | on true relative time) and absolute (ev_periodic, based on wallclock time) |
|
|
221 | timers. |
|
|
222 | |
|
|
223 | AnyEvent always prefers relative timers, if available, matching the |
|
|
224 | AnyEvent API. |
|
|
225 | |
|
|
226 | =head2 SIGNAL WATCHERS |
|
|
227 | |
|
|
228 | You can watch for signals using a signal watcher, C<signal> is the signal |
|
|
229 | I<name> without any C<SIG> prefix, C<cb> is the Perl callback to |
|
|
230 | be invoked whenever a signal occurs. |
|
|
231 | |
|
|
232 | Multiple signal occurances can be clumped together into one callback |
|
|
233 | invocation, and callback invocation will be synchronous. synchronous means |
|
|
234 | that it might take a while until the signal gets handled by the process, |
|
|
235 | but it is guarenteed not to interrupt any other callbacks. |
|
|
236 | |
|
|
237 | The main advantage of using these watchers is that you can share a signal |
|
|
238 | between multiple watchers. |
|
|
239 | |
|
|
240 | This watcher might use C<%SIG>, so programs overwriting those signals |
|
|
241 | directly will likely not work correctly. |
|
|
242 | |
|
|
243 | Example: exit on SIGINT |
|
|
244 | |
|
|
245 | my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); |
|
|
246 | |
|
|
247 | =head2 CHILD PROCESS WATCHERS |
|
|
248 | |
|
|
249 | You can also watch on a child process exit and catch its exit status. |
|
|
250 | |
|
|
251 | The child process is specified by the C<pid> argument (if set to C<0>, it |
|
|
252 | watches for any child process exit). The watcher will trigger as often |
|
|
253 | as status change for the child are received. This works by installing a |
|
|
254 | signal handler for C<SIGCHLD>. The callback will be called with the pid |
|
|
255 | and exit status (as returned by waitpid). |
|
|
256 | |
|
|
257 | Example: wait for pid 1333 |
|
|
258 | |
|
|
259 | my $w = AnyEvent->child ( |
|
|
260 | pid => 1333, |
|
|
261 | cb => sub { |
|
|
262 | my ($pid, $status) = @_; |
|
|
263 | warn "pid $pid exited with status $status"; |
|
|
264 | }, |
|
|
265 | ); |
|
|
266 | |
161 | =head2 CONDITION WATCHERS |
267 | =head2 CONDITION VARIABLES |
162 | |
268 | |
163 | Condition watchers can be created by calling the C<< AnyEvent->condvar >> |
269 | Condition variables can be created by calling the C<< AnyEvent->condvar >> |
164 | method without any arguments. |
270 | method without any arguments. |
165 | |
271 | |
166 | A condition watcher watches for a condition - precisely that the C<< |
272 | A condition variable waits for a condition - precisely that the C<< |
167 | ->broadcast >> method has been called. |
273 | ->broadcast >> method has been called. |
168 | |
274 | |
|
|
275 | They are very useful to signal that a condition has been fulfilled, for |
|
|
276 | example, if you write a module that does asynchronous http requests, |
|
|
277 | then a condition variable would be the ideal candidate to signal the |
|
|
278 | availability of results. |
|
|
279 | |
|
|
280 | You can also use condition variables to block your main program until |
|
|
281 | an event occurs - for example, you could C<< ->wait >> in your main |
|
|
282 | program until the user clicks the Quit button in your app, which would C<< |
|
|
283 | ->broadcast >> the "quit" event. |
|
|
284 | |
169 | Note that condition watchers recurse into the event loop - if you have |
285 | Note that condition variables recurse into the event loop - if you have |
170 | two watchers that call C<< ->wait >> in a round-robbin fashion, you |
286 | two pirces of code that call C<< ->wait >> in a round-robbin fashion, you |
171 | lose. Therefore, condition watchers are good to export to your caller, but |
287 | lose. Therefore, condition variables are good to export to your caller, but |
172 | you should avoid making a blocking wait, at least in callbacks, as this |
288 | you should avoid making a blocking wait yourself, at least in callbacks, |
173 | usually asks for trouble. |
289 | as this asks for trouble. |
174 | |
290 | |
175 | The watcher has only two methods: |
291 | This object has two methods: |
176 | |
292 | |
177 | =over 4 |
293 | =over 4 |
178 | |
294 | |
179 | =item $cv->wait |
295 | =item $cv->wait |
180 | |
296 | |
… | |
… | |
183 | |
299 | |
184 | You can only wait once on a condition - additional calls will return |
300 | You can only wait once on a condition - additional calls will return |
185 | immediately. |
301 | immediately. |
186 | |
302 | |
187 | Not all event models support a blocking wait - some die in that case |
303 | Not all event models support a blocking wait - some die in that case |
188 | (programs might want to do that so they stay interactive), so I<if you |
304 | (programs might want to do that to stay interactive), so I<if you are |
189 | are using this from a module, never require a blocking wait>, but let the |
305 | using this from a module, never require a blocking wait>, but let the |
190 | caller decide wether the call will block or not (for example, by coupling |
306 | caller decide whether the call will block or not (for example, by coupling |
191 | condition variables with some kind of request results and supporting |
307 | condition variables with some kind of request results and supporting |
192 | callbacks so the caller knows that getting the result will not block, |
308 | callbacks so the caller knows that getting the result will not block, |
193 | while still suppporting blocking waits if the caller so desires). |
309 | while still suppporting blocking waits if the caller so desires). |
194 | |
310 | |
195 | Another reason I<never> to C<< ->wait >> in a module is that you cannot |
311 | Another reason I<never> to C<< ->wait >> in a module is that you cannot |
196 | sensibly have two C<< ->wait >>'s in parallel, as that would require |
312 | sensibly have two C<< ->wait >>'s in parallel, as that would require |
197 | multiple interpreters or coroutines/threads, none of which C<AnyEvent> |
313 | multiple interpreters or coroutines/threads, none of which C<AnyEvent> |
198 | can supply (the coroutine-aware backends C<Coro::EV> and C<Coro::Event> |
314 | can supply (the coroutine-aware backends L<AnyEvent::Impl::CoroEV> and |
199 | explicitly support concurrent C<< ->wait >>'s from different coroutines, |
315 | L<AnyEvent::Impl::CoroEvent> explicitly support concurrent C<< ->wait >>'s |
200 | however). |
316 | from different coroutines, however). |
201 | |
317 | |
202 | =item $cv->broadcast |
318 | =item $cv->broadcast |
203 | |
319 | |
204 | Flag the condition as ready - a running C<< ->wait >> and all further |
320 | Flag the condition as ready - a running C<< ->wait >> and all further |
205 | calls to C<wait> will return after this method has been called. If nobody |
321 | calls to C<wait> will (eventually) return after this method has been |
206 | is waiting the broadcast will be remembered.. |
322 | called. If nobody is waiting the broadcast will be remembered.. |
|
|
323 | |
|
|
324 | =back |
207 | |
325 | |
208 | Example: |
326 | Example: |
209 | |
327 | |
210 | # wait till the result is ready |
328 | # wait till the result is ready |
211 | my $result_ready = AnyEvent->condvar; |
329 | my $result_ready = AnyEvent->condvar; |
212 | |
330 | |
213 | # do something such as adding a timer |
331 | # do something such as adding a timer |
214 | # or socket watcher the calls $result_ready->broadcast |
332 | # or socket watcher the calls $result_ready->broadcast |
215 | # when the "result" is ready. |
333 | # when the "result" is ready. |
|
|
334 | # in this case, we simply use a timer: |
|
|
335 | my $w = AnyEvent->timer ( |
|
|
336 | after => 1, |
|
|
337 | cb => sub { $result_ready->broadcast }, |
|
|
338 | ); |
216 | |
339 | |
|
|
340 | # this "blocks" (while handling events) till the watcher |
|
|
341 | # calls broadcast |
217 | $result_ready->wait; |
342 | $result_ready->wait; |
218 | |
343 | |
219 | =back |
344 | =head1 GLOBAL VARIABLES AND FUNCTIONS |
220 | |
|
|
221 | =head2 SIGNAL WATCHERS |
|
|
222 | |
|
|
223 | You can listen for signals using a signal watcher, C<signal> is the signal |
|
|
224 | I<name> without any C<SIG> prefix. Multiple signals events can be clumped |
|
|
225 | together into one callback invocation, and callback invocation might or |
|
|
226 | might not be asynchronous. |
|
|
227 | |
|
|
228 | These watchers might use C<%SIG>, so programs overwriting those signals |
|
|
229 | directly will likely not work correctly. |
|
|
230 | |
|
|
231 | Example: exit on SIGINT |
|
|
232 | |
|
|
233 | my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); |
|
|
234 | |
|
|
235 | =head2 CHILD PROCESS WATCHERS |
|
|
236 | |
|
|
237 | You can also listen for the status of a child process specified by the |
|
|
238 | C<pid> argument (or any child if the pid argument is 0). The watcher will |
|
|
239 | trigger as often as status change for the child are received. This works |
|
|
240 | by installing a signal handler for C<SIGCHLD>. The callback will be called with |
|
|
241 | the pid and exit status (as returned by waitpid). |
|
|
242 | |
|
|
243 | Example: wait for pid 1333 |
|
|
244 | |
|
|
245 | my $w = AnyEvent->child (pid => 1333, cb => sub { warn "exit status $?" }); |
|
|
246 | |
|
|
247 | =head1 GLOBALS |
|
|
248 | |
345 | |
249 | =over 4 |
346 | =over 4 |
250 | |
347 | |
251 | =item $AnyEvent::MODEL |
348 | =item $AnyEvent::MODEL |
252 | |
349 | |
… | |
… | |
257 | AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). |
354 | AnyEvent has been extended at runtime (e.g. in I<rxvt-unicode>). |
258 | |
355 | |
259 | The known classes so far are: |
356 | The known classes so far are: |
260 | |
357 | |
261 | AnyEvent::Impl::CoroEV based on Coro::EV, best choice. |
358 | AnyEvent::Impl::CoroEV based on Coro::EV, best choice. |
262 | AnyEvent::Impl::EV based on EV (an interface to libev, also best choice). |
|
|
263 | AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice. |
359 | AnyEvent::Impl::CoroEvent based on Coro::Event, second best choice. |
|
|
360 | AnyEvent::Impl::EV based on EV (an interface to libev, best choice). |
264 | AnyEvent::Impl::Event based on Event, also second best choice :) |
361 | AnyEvent::Impl::Event based on Event, second best choice. |
265 | AnyEvent::Impl::Glib based on Glib, third-best choice. |
362 | AnyEvent::Impl::Glib based on Glib, third-best choice. |
266 | AnyEvent::Impl::Tk based on Tk, very bad choice. |
363 | AnyEvent::Impl::Tk based on Tk, very bad choice. |
267 | AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable. |
364 | AnyEvent::Impl::Perl pure-perl implementation, inefficient but portable. |
|
|
365 | AnyEvent::Impl::Qt based on Qt, cannot be autoprobed (see its docs). |
|
|
366 | AnyEvent::Impl::EventLib based on Event::Lib, leaks memory and worse. |
268 | |
367 | |
269 | =item AnyEvent::detect |
368 | =item AnyEvent::detect |
270 | |
369 | |
271 | Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model if |
370 | Returns C<$AnyEvent::MODEL>, forcing autodetection of the event model |
272 | necessary. You should only call this function right before you would have |
371 | if necessary. You should only call this function right before you would |
273 | created an AnyEvent watcher anyway, that is, very late at runtime. |
372 | have created an AnyEvent watcher anyway, that is, as late as possible at |
|
|
373 | runtime. |
274 | |
374 | |
275 | =back |
375 | =back |
276 | |
376 | |
277 | =head1 WHAT TO DO IN A MODULE |
377 | =head1 WHAT TO DO IN A MODULE |
278 | |
378 | |
279 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
379 | As a module author, you should C<use AnyEvent> and call AnyEvent methods |
280 | freely, but you should not load a specific event module or rely on it. |
380 | freely, but you should not load a specific event module or rely on it. |
281 | |
381 | |
282 | Be careful when you create watchers in the module body - Anyevent will |
382 | Be careful when you create watchers in the module body - AnyEvent will |
283 | decide which event module to use as soon as the first method is called, so |
383 | decide which event module to use as soon as the first method is called, so |
284 | by calling AnyEvent in your module body you force the user of your module |
384 | by calling AnyEvent in your module body you force the user of your module |
285 | to load the event module first. |
385 | to load the event module first. |
286 | |
386 | |
|
|
387 | Never call C<< ->wait >> on a condition variable unless you I<know> that |
|
|
388 | the C<< ->broadcast >> method has been called on it already. This is |
|
|
389 | because it will stall the whole program, and the whole point of using |
|
|
390 | events is to stay interactive. |
|
|
391 | |
|
|
392 | It is fine, however, to call C<< ->wait >> when the user of your module |
|
|
393 | requests it (i.e. if you create a http request object ad have a method |
|
|
394 | called C<results> that returns the results, it should call C<< ->wait >> |
|
|
395 | freely, as the user of your module knows what she is doing. always). |
|
|
396 | |
287 | =head1 WHAT TO DO IN THE MAIN PROGRAM |
397 | =head1 WHAT TO DO IN THE MAIN PROGRAM |
288 | |
398 | |
289 | There will always be a single main program - the only place that should |
399 | There will always be a single main program - the only place that should |
290 | dictate which event model to use. |
400 | dictate which event model to use. |
291 | |
401 | |
292 | If it doesn't care, it can just "use AnyEvent" and use it itself, or not |
402 | If it doesn't care, it can just "use AnyEvent" and use it itself, or not |
293 | do anything special and let AnyEvent decide which implementation to chose. |
403 | do anything special (it does not need to be event-based) and let AnyEvent |
|
|
404 | decide which implementation to chose if some module relies on it. |
294 | |
405 | |
295 | If the main program relies on a specific event model (for example, in Gtk2 |
406 | If the main program relies on a specific event model. For example, in |
296 | programs you have to rely on either Glib or Glib::Event), you should load |
407 | Gtk2 programs you have to rely on the Glib module. You should load the |
297 | it before loading AnyEvent or any module that uses it, generally, as early |
408 | event module before loading AnyEvent or any module that uses it: generally |
298 | as possible. The reason is that modules might create watchers when they |
409 | speaking, you should load it as early as possible. The reason is that |
299 | are loaded, and AnyEvent will decide on the event model to use as soon as |
410 | modules might create watchers when they are loaded, and AnyEvent will |
300 | it creates watchers, and it might chose the wrong one unless you load the |
411 | decide on the event model to use as soon as it creates watchers, and it |
301 | correct one yourself. |
412 | might chose the wrong one unless you load the correct one yourself. |
302 | |
413 | |
303 | You can chose to use a rather inefficient pure-perl implementation by |
414 | You can chose to use a rather inefficient pure-perl implementation by |
304 | loading the C<AnyEvent::Impl::Perl> module, but letting AnyEvent chose is |
415 | loading the C<AnyEvent::Impl::Perl> module, which gives you similar |
305 | generally better. |
416 | behaviour everywhere, but letting AnyEvent chose is generally better. |
306 | |
417 | |
307 | =cut |
418 | =cut |
308 | |
419 | |
309 | package AnyEvent; |
420 | package AnyEvent; |
310 | |
421 | |
311 | no warnings; |
422 | no warnings; |
312 | use strict; |
423 | use strict; |
313 | |
424 | |
314 | use Carp; |
425 | use Carp; |
315 | |
426 | |
316 | our $VERSION = '3.0'; |
427 | our $VERSION = '3.2'; |
317 | our $MODEL; |
428 | our $MODEL; |
318 | |
429 | |
319 | our $AUTOLOAD; |
430 | our $AUTOLOAD; |
320 | our @ISA; |
431 | our @ISA; |
321 | |
432 | |
… | |
… | |
323 | |
434 | |
324 | our @REGISTRY; |
435 | our @REGISTRY; |
325 | |
436 | |
326 | my @models = ( |
437 | my @models = ( |
327 | [Coro::EV:: => AnyEvent::Impl::CoroEV::], |
438 | [Coro::EV:: => AnyEvent::Impl::CoroEV::], |
|
|
439 | [Coro::Event:: => AnyEvent::Impl::CoroEvent::], |
328 | [EV:: => AnyEvent::Impl::EV::], |
440 | [EV:: => AnyEvent::Impl::EV::], |
329 | [Coro::Event:: => AnyEvent::Impl::CoroEvent::], |
|
|
330 | [Event:: => AnyEvent::Impl::Event::], |
441 | [Event:: => AnyEvent::Impl::Event::], |
331 | [Glib:: => AnyEvent::Impl::Glib::], |
442 | [Glib:: => AnyEvent::Impl::Glib::], |
332 | [Tk:: => AnyEvent::Impl::Tk::], |
443 | [Tk:: => AnyEvent::Impl::Tk::], |
333 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
444 | [AnyEvent::Impl::Perl:: => AnyEvent::Impl::Perl::], |
334 | ); |
445 | ); |
|
|
446 | my @models_detect = ( |
|
|
447 | [Qt:: => AnyEvent::Impl::Qt::], # requires special main program |
|
|
448 | [Event::Lib:: => AnyEvent::Impl::EventLib::], # too buggy |
|
|
449 | ); |
335 | |
450 | |
336 | our %method = map +($_ => 1), qw(io timer condvar broadcast wait signal one_event DESTROY); |
451 | our %method = map +($_ => 1), qw(io timer signal child condvar broadcast wait one_event DESTROY); |
337 | |
452 | |
338 | sub detect() { |
453 | sub detect() { |
339 | unless ($MODEL) { |
454 | unless ($MODEL) { |
340 | no strict 'refs'; |
455 | no strict 'refs'; |
341 | |
456 | |
|
|
457 | if ($ENV{PERL_ANYEVENT_MODEL} =~ /^([a-zA-Z]+)$/) { |
|
|
458 | my $model = "AnyEvent::Impl::$1"; |
|
|
459 | if (eval "require $model") { |
|
|
460 | $MODEL = $model; |
|
|
461 | warn "AnyEvent: loaded model '$model' (forced by \$PERL_ANYEVENT_MODEL), using it.\n" if $verbose > 1; |
|
|
462 | } else { |
|
|
463 | warn "AnyEvent: unable to load model '$model' (from \$PERL_ANYEVENT_MODEL):\n$@" if $verbose; |
|
|
464 | } |
|
|
465 | } |
|
|
466 | |
342 | # check for already loaded models |
467 | # check for already loaded models |
|
|
468 | unless ($MODEL) { |
343 | for (@REGISTRY, @models) { |
469 | for (@REGISTRY, @models, @models_detect) { |
344 | my ($package, $model) = @$_; |
470 | my ($package, $model) = @$_; |
345 | if (${"$package\::VERSION"} > 0) { |
471 | if (${"$package\::VERSION"} > 0) { |
346 | if (eval "require $model") { |
472 | if (eval "require $model") { |
347 | $MODEL = $model; |
473 | $MODEL = $model; |
348 | warn "AnyEvent: found model '$model', using it.\n" if $verbose > 1; |
474 | warn "AnyEvent: autodetected model '$model', using it.\n" if $verbose > 1; |
349 | last; |
475 | last; |
|
|
476 | } |
350 | } |
477 | } |
351 | } |
478 | } |
352 | } |
|
|
353 | |
479 | |
354 | unless ($MODEL) { |
480 | unless ($MODEL) { |
355 | # try to load a model |
481 | # try to load a model |
356 | |
482 | |
357 | for (@REGISTRY, @models) { |
483 | for (@REGISTRY, @models) { |
358 | my ($package, $model) = @$_; |
484 | my ($package, $model) = @$_; |
359 | if (eval "require $package" |
485 | if (eval "require $package" |
360 | and ${"$package\::VERSION"} > 0 |
486 | and ${"$package\::VERSION"} > 0 |
361 | and eval "require $model") { |
487 | and eval "require $model") { |
362 | $MODEL = $model; |
488 | $MODEL = $model; |
363 | warn "AnyEvent: autoprobed and loaded model '$model', using it.\n" if $verbose > 1; |
489 | warn "AnyEvent: autoprobed model '$model', using it.\n" if $verbose > 1; |
364 | last; |
490 | last; |
|
|
491 | } |
365 | } |
492 | } |
|
|
493 | |
|
|
494 | $MODEL |
|
|
495 | or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event) or Glib."; |
366 | } |
496 | } |
367 | |
|
|
368 | $MODEL |
|
|
369 | or die "No event module selected for AnyEvent and autodetect failed. Install any one of these modules: EV (or Coro+EV), Event (or Coro+Event), Glib or Tk."; |
|
|
370 | } |
497 | } |
371 | |
498 | |
372 | unshift @ISA, $MODEL; |
499 | unshift @ISA, $MODEL; |
373 | push @{"$MODEL\::ISA"}, "AnyEvent::Base"; |
500 | push @{"$MODEL\::ISA"}, "AnyEvent::Base"; |
374 | } |
501 | } |
… | |
… | |
485 | undef $CHLD_W unless keys %PID_CB; |
612 | undef $CHLD_W unless keys %PID_CB; |
486 | } |
613 | } |
487 | |
614 | |
488 | =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
615 | =head1 SUPPLYING YOUR OWN EVENT MODEL INTERFACE |
489 | |
616 | |
|
|
617 | This is an advanced topic that you do not normally need to use AnyEvent in |
|
|
618 | a module. This section is only of use to event loop authors who want to |
|
|
619 | provide AnyEvent compatibility. |
|
|
620 | |
490 | If you need to support another event library which isn't directly |
621 | If you need to support another event library which isn't directly |
491 | supported by AnyEvent, you can supply your own interface to it by |
622 | supported by AnyEvent, you can supply your own interface to it by |
492 | pushing, before the first watcher gets created, the package name of |
623 | pushing, before the first watcher gets created, the package name of |
493 | the event module and the package name of the interface to use onto |
624 | the event module and the package name of the interface to use onto |
494 | C<@AnyEvent::REGISTRY>. You can do that before and even without loading |
625 | C<@AnyEvent::REGISTRY>. You can do that before and even without loading |
495 | AnyEvent. |
626 | AnyEvent, so it is reasonably cheap. |
496 | |
627 | |
497 | Example: |
628 | Example: |
498 | |
629 | |
499 | push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::]; |
630 | push @AnyEvent::REGISTRY, [urxvt => urxvt::anyevent::]; |
500 | |
631 | |
501 | This tells AnyEvent to (literally) use the C<urxvt::anyevent::> |
632 | This tells AnyEvent to (literally) use the C<urxvt::anyevent::> |
502 | package/class when it finds the C<urxvt> package/module is loaded. When |
633 | package/class when it finds the C<urxvt> package/module is already loaded. |
|
|
634 | |
503 | AnyEvent is loaded and asked to find a suitable event model, it will |
635 | When AnyEvent is loaded and asked to find a suitable event model, it |
504 | first check for the presence of urxvt. |
636 | will first check for the presence of urxvt by trying to C<use> the |
|
|
637 | C<urxvt::anyevent> module. |
505 | |
638 | |
506 | The class should provide implementations for all watcher types (see |
639 | The class should provide implementations for all watcher types. See |
507 | L<AnyEvent::Impl::Event> (source code), L<AnyEvent::Impl::Glib> |
640 | L<AnyEvent::Impl::EV> (source code), L<AnyEvent::Impl::Glib> (Source code) |
508 | (Source code) and so on for actual examples, use C<perldoc -m |
641 | and so on for actual examples. Use C<perldoc -m AnyEvent::Impl::Glib> to |
509 | AnyEvent::Impl::Glib> to see the sources). |
642 | see the sources. |
510 | |
643 | |
|
|
644 | If you don't provide C<signal> and C<child> watchers than AnyEvent will |
|
|
645 | provide suitable (hopefully) replacements. |
|
|
646 | |
511 | The above isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt) |
647 | The above example isn't fictitious, the I<rxvt-unicode> (a.k.a. urxvt) |
512 | uses the above line as-is. An interface isn't included in AnyEvent |
648 | terminal emulator uses the above line as-is. An interface isn't included |
513 | because it doesn't make sense outside the embedded interpreter inside |
649 | in AnyEvent because it doesn't make sense outside the embedded interpreter |
514 | I<rxvt-unicode>, and it is updated and maintained as part of the |
650 | inside I<rxvt-unicode>, and it is updated and maintained as part of the |
515 | I<rxvt-unicode> distribution. |
651 | I<rxvt-unicode> distribution. |
516 | |
652 | |
517 | I<rxvt-unicode> also cheats a bit by not providing blocking access to |
653 | I<rxvt-unicode> also cheats a bit by not providing blocking access to |
518 | condition variables: code blocking while waiting for a condition will |
654 | condition variables: code blocking while waiting for a condition will |
519 | C<die>. This still works with most modules/usages, and blocking calls must |
655 | C<die>. This still works with most modules/usages, and blocking calls must |
520 | not be in an interactive application, so it makes sense. |
656 | not be done in an interactive application, so it makes sense. |
521 | |
657 | |
522 | =head1 ENVIRONMENT VARIABLES |
658 | =head1 ENVIRONMENT VARIABLES |
523 | |
659 | |
524 | The following environment variables are used by this module: |
660 | The following environment variables are used by this module: |
525 | |
661 | |
526 | C<PERL_ANYEVENT_VERBOSE> when set to C<2> or higher, reports which event |
662 | =over 4 |
527 | model gets used. |
|
|
528 | |
663 | |
|
|
664 | =item C<PERL_ANYEVENT_VERBOSE> |
|
|
665 | |
|
|
666 | By default, AnyEvent will be completely silent except in fatal |
|
|
667 | conditions. You can set this environment variable to make AnyEvent more |
|
|
668 | talkative. |
|
|
669 | |
|
|
670 | When set to C<1> or higher, causes AnyEvent to warn about unexpected |
|
|
671 | conditions, such as not being able to load the event model specified by |
|
|
672 | C<PERL_ANYEVENT_MODEL>. |
|
|
673 | |
|
|
674 | When set to C<2> or higher, cause AnyEvent to report to STDERR which event |
|
|
675 | model it chooses. |
|
|
676 | |
|
|
677 | =item C<PERL_ANYEVENT_MODEL> |
|
|
678 | |
|
|
679 | This can be used to specify the event model to be used by AnyEvent, before |
|
|
680 | autodetection and -probing kicks in. It must be a string consisting |
|
|
681 | entirely of ASCII letters. The string C<AnyEvent::Impl::> gets prepended |
|
|
682 | and the resulting module name is loaded and if the load was successful, |
|
|
683 | used as event model. If it fails to load AnyEvent will proceed with |
|
|
684 | autodetection and -probing. |
|
|
685 | |
|
|
686 | This functionality might change in future versions. |
|
|
687 | |
|
|
688 | For example, to force the pure perl model (L<AnyEvent::Impl::Perl>) you |
|
|
689 | could start your program like this: |
|
|
690 | |
|
|
691 | PERL_ANYEVENT_MODEL=Perl perl ... |
|
|
692 | |
|
|
693 | =back |
|
|
694 | |
529 | =head1 EXAMPLE |
695 | =head1 EXAMPLE PROGRAM |
530 | |
696 | |
531 | The following program uses an io watcher to read data from stdin, a timer |
697 | The following program uses an IO watcher to read data from STDIN, a timer |
532 | to display a message once per second, and a condvar to exit the program |
698 | to display a message once per second, and a condition variable to quit the |
533 | when the user enters quit: |
699 | program when the user enters quit: |
534 | |
700 | |
535 | use AnyEvent; |
701 | use AnyEvent; |
536 | |
702 | |
537 | my $cv = AnyEvent->condvar; |
703 | my $cv = AnyEvent->condvar; |
538 | |
704 | |
539 | my $io_watcher = AnyEvent->io (fh => \*STDIN, poll => 'r', cb => sub { |
705 | my $io_watcher = AnyEvent->io ( |
|
|
706 | fh => \*STDIN, |
|
|
707 | poll => 'r', |
|
|
708 | cb => sub { |
540 | warn "io event <$_[0]>\n"; # will always output <r> |
709 | warn "io event <$_[0]>\n"; # will always output <r> |
541 | chomp (my $input = <STDIN>); # read a line |
710 | chomp (my $input = <STDIN>); # read a line |
542 | warn "read: $input\n"; # output what has been read |
711 | warn "read: $input\n"; # output what has been read |
543 | $cv->broadcast if $input =~ /^q/i; # quit program if /^q/i |
712 | $cv->broadcast if $input =~ /^q/i; # quit program if /^q/i |
|
|
713 | }, |
544 | }); |
714 | ); |
545 | |
715 | |
546 | my $time_watcher; # can only be used once |
716 | my $time_watcher; # can only be used once |
547 | |
717 | |
548 | sub new_timer { |
718 | sub new_timer { |
549 | $timer = AnyEvent->timer (after => 1, cb => sub { |
719 | $timer = AnyEvent->timer (after => 1, cb => sub { |
… | |
… | |
631 | $txn->{finished}->wait; |
801 | $txn->{finished}->wait; |
632 | return $txn->{result}; |
802 | return $txn->{result}; |
633 | |
803 | |
634 | The actual code goes further and collects all errors (C<die>s, exceptions) |
804 | The actual code goes further and collects all errors (C<die>s, exceptions) |
635 | that occured during request processing. The C<result> method detects |
805 | that occured during request processing. The C<result> method detects |
636 | wether an exception as thrown (it is stored inside the $txn object) |
806 | whether an exception as thrown (it is stored inside the $txn object) |
637 | and just throws the exception, which means connection errors and other |
807 | and just throws the exception, which means connection errors and other |
638 | problems get reported tot he code that tries to use the result, not in a |
808 | problems get reported tot he code that tries to use the result, not in a |
639 | random callback. |
809 | random callback. |
640 | |
810 | |
641 | All of this enables the following usage styles: |
811 | All of this enables the following usage styles: |
… | |
… | |
676 | $quit->broadcast; |
846 | $quit->broadcast; |
677 | }); |
847 | }); |
678 | |
848 | |
679 | $quit->wait; |
849 | $quit->wait; |
680 | |
850 | |
|
|
851 | =head1 FORK |
|
|
852 | |
|
|
853 | Most event libraries are not fork-safe. The ones who are usually are |
|
|
854 | because they are so inefficient. Only L<EV> is fully fork-aware. |
|
|
855 | |
|
|
856 | If you have to fork, you must either do so I<before> creating your first |
|
|
857 | watcher OR you must not use AnyEvent at all in the child. |
|
|
858 | |
|
|
859 | =head1 SECURITY CONSIDERATIONS |
|
|
860 | |
|
|
861 | AnyEvent can be forced to load any event model via |
|
|
862 | $ENV{PERL_ANYEVENT_MODEL}. While this cannot (to my knowledge) be used to |
|
|
863 | execute arbitrary code or directly gain access, it can easily be used to |
|
|
864 | make the program hang or malfunction in subtle ways, as AnyEvent watchers |
|
|
865 | will not be active when the program uses a different event model than |
|
|
866 | specified in the variable. |
|
|
867 | |
|
|
868 | You can make AnyEvent completely ignore this variable by deleting it |
|
|
869 | before the first watcher gets created, e.g. with a C<BEGIN> block: |
|
|
870 | |
|
|
871 | BEGIN { delete $ENV{PERL_ANYEVENT_MODEL} } |
|
|
872 | |
|
|
873 | use AnyEvent; |
|
|
874 | |
681 | =head1 SEE ALSO |
875 | =head1 SEE ALSO |
682 | |
876 | |
683 | Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>, |
877 | Event modules: L<Coro::EV>, L<EV>, L<EV::Glib>, L<Glib::EV>, |
684 | L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>. |
878 | L<Coro::Event>, L<Event>, L<Glib::Event>, L<Glib>, L<Coro>, L<Tk>, |
|
|
879 | L<Event::Lib>, L<Qt>. |
685 | |
880 | |
686 | Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>, |
881 | Implementations: L<AnyEvent::Impl::CoroEV>, L<AnyEvent::Impl::EV>, |
687 | L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>, |
882 | L<AnyEvent::Impl::CoroEvent>, L<AnyEvent::Impl::Event>, L<AnyEvent::Impl::Glib>, |
688 | L<AnyEvent::Impl::Glib>, L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>. |
883 | L<AnyEvent::Impl::Tk>, L<AnyEvent::Impl::Perl>, L<AnyEvent::Impl::EventLib>, |
|
|
884 | L<AnyEvent::Impl::Qt>. |
689 | |
885 | |
690 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>. |
886 | Nontrivial usage examples: L<Net::FCP>, L<Net::XMPP2>. |
691 | |
887 | |
692 | =head1 |
888 | =head1 AUTHOR |
|
|
889 | |
|
|
890 | Marc Lehmann <schmorp@schmorp.de> |
|
|
891 | http://home.schmorp.de/ |
693 | |
892 | |
694 | =cut |
893 | =cut |
695 | |
894 | |
696 | 1 |
895 | 1 |
697 | |
896 | |