… | |
… | |
84 | chomp (my $input = <STDIN>); |
84 | chomp (my $input = <STDIN>); |
85 | warn "read: $input\n"; |
85 | warn "read: $input\n"; |
86 | undef $w; |
86 | undef $w; |
87 | }); |
87 | }); |
88 | |
88 | |
89 | TIMER WATCHERS |
89 | TIME WATCHERS |
90 | You can create a timer watcher by calling the "AnyEvent->timer" method |
90 | You can create a time watcher by calling the "AnyEvent->timer" method |
91 | with the following mandatory arguments: |
91 | with the following mandatory arguments: |
92 | |
92 | |
93 | "after" after how many seconds (fractions are supported) should the |
93 | "after" after how many seconds (fractions are supported) should the |
94 | timer activate. "cb" the callback to invoke. |
94 | timer activate. "cb" the callback to invoke. |
95 | |
95 | |
… | |
… | |
145 | # or socket watcher the calls $result_ready->broadcast |
145 | # or socket watcher the calls $result_ready->broadcast |
146 | # when the "result" is ready. |
146 | # when the "result" is ready. |
147 | |
147 | |
148 | $result_ready->wait; |
148 | $result_ready->wait; |
149 | |
149 | |
|
|
150 | SIGNAL WATCHERS |
|
|
151 | You can listen for signals using a signal watcher, "signal" is the |
|
|
152 | signal *name* without any "SIG" prefix. Multiple signals events can be |
|
|
153 | clumped together into one callback invocation, and callback invocation |
|
|
154 | might or might not be asynchronous. |
|
|
155 | |
|
|
156 | These watchers might use %SIG, so programs overwriting those signals |
|
|
157 | directly will likely not work correctly. |
|
|
158 | |
|
|
159 | Example: exit on SIGINT |
|
|
160 | |
|
|
161 | my $w = AnyEvent->signal (signal => "INT", cb => sub { exit 1 }); |
|
|
162 | |
|
|
163 | CHILD PROCESS WATCHERS |
|
|
164 | You can also listen for the status of a child process specified by the |
|
|
165 | "pid" argument. The watcher will only trigger once. This works by |
|
|
166 | installing a signal handler for "SIGCHLD". |
|
|
167 | |
|
|
168 | Example: wait for pid 1333 |
|
|
169 | |
|
|
170 | my $w = AnyEvent->child (pid => 1333, cb => sub { warn "exit status $?" }); |
|
|
171 | |
|
|
172 | GLOBALS |
|
|
173 | $AnyEvent::MODEL |
|
|
174 | Contains "undef" until the first watcher is being created. Then it |
|
|
175 | contains the event model that is being used, which is the name of |
|
|
176 | the Perl class implementing the model. This class is usually one of |
|
|
177 | the "AnyEvent::Impl:xxx" modules, but can be any other class in the |
|
|
178 | case AnyEvent has been extended at runtime (e.g. in *rxvt-unicode*). |
|
|
179 | |
|
|
180 | The known classes so far are: |
|
|
181 | |
|
|
182 | AnyEvent::Impl::Coro based on Coro::Event, best choise. |
|
|
183 | AnyEvent::Impl::Event based on Event, also best choice :) |
|
|
184 | AnyEvent::Impl::Glib based on Glib, second-best choice. |
|
|
185 | AnyEvent::Impl::Tk based on Tk, very bad choice. |
|
|
186 | AnyEvent::Impl::Perl pure-perl implementation, inefficient. |
|
|
187 | |
|
|
188 | AnyEvent::detect |
|
|
189 | Returns $AnyEvent::MODEL, forcing autodetection of the event model |
|
|
190 | if necessary. You should only call this function right before you |
|
|
191 | would have created an AnyEvent watcher anyway, that is, very late at |
|
|
192 | runtime. |
|
|
193 | |
150 | WHAT TO DO IN A MODULE |
194 | WHAT TO DO IN A MODULE |
151 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
195 | As a module author, you should "use AnyEvent" and call AnyEvent methods |
152 | freely, but you should not load a specific event module or rely on it. |
196 | freely, but you should not load a specific event module or rely on it. |
153 | |
197 | |
154 | Be careful when you create watchers in the module body - Anyevent will |
198 | Be careful when you create watchers in the module body - Anyevent will |
… | |
… | |
191 | This tells AnyEvent to (literally) use the "urxvt::anyevent::" |
235 | This tells AnyEvent to (literally) use the "urxvt::anyevent::" |
192 | package/class when it finds the "urxvt" package/module is loaded. When |
236 | package/class when it finds the "urxvt" package/module is loaded. When |
193 | AnyEvent is loaded and asked to find a suitable event model, it will |
237 | AnyEvent is loaded and asked to find a suitable event model, it will |
194 | first check for the presence of urxvt. |
238 | first check for the presence of urxvt. |
195 | |
239 | |
196 | The class should prove implementations for all watcher types (see |
240 | The class should provide implementations for all watcher types (see |
197 | AnyEvent::Impl::Event (source code), AnyEvent::Impl::Glib (Source code) |
241 | AnyEvent::Impl::Event (source code), AnyEvent::Impl::Glib (Source code) |
198 | and so on for actual examples, use "perldoc -m AnyEvent::Impl::Glib" to |
242 | and so on for actual examples, use "perldoc -m AnyEvent::Impl::Glib" to |
199 | see the sources). |
243 | see the sources). |
200 | |
244 | |
201 | The above isn't fictitious, the *rxvt-unicode* (a.k.a. urxvt) uses the |
245 | The above isn't fictitious, the *rxvt-unicode* (a.k.a. urxvt) uses the |
… | |
… | |
205 | *rxvt-unicode* distribution. |
249 | *rxvt-unicode* distribution. |
206 | |
250 | |
207 | *rxvt-unicode* also cheats a bit by not providing blocking access to |
251 | *rxvt-unicode* also cheats a bit by not providing blocking access to |
208 | condition variables: code blocking while waiting for a condition will |
252 | condition variables: code blocking while waiting for a condition will |
209 | "die". This still works with most modules/usages, and blocking calls |
253 | "die". This still works with most modules/usages, and blocking calls |
210 | must not be in an interactive appliation, so it makes sense. |
254 | must not be in an interactive application, so it makes sense. |
211 | |
255 | |
212 | ENVIRONMENT VARIABLES |
256 | ENVIRONMENT VARIABLES |
213 | The following environment variables are used by this module: |
257 | The following environment variables are used by this module: |
214 | |
258 | |
215 | "PERL_ANYEVENT_VERBOSE" when set to 2 or higher, reports which event |
259 | "PERL_ANYEVENT_VERBOSE" when set to 2 or higher, reports which event |