| … | |
… | |
| 174 | =item ev_tstamp ev_time () |
174 | =item ev_tstamp ev_time () |
| 175 | |
175 | |
| 176 | Returns the current time as libev would use it. Please note that the |
176 | Returns the current time as libev would use it. Please note that the |
| 177 | C<ev_now> function is usually faster and also often returns the timestamp |
177 | C<ev_now> function is usually faster and also often returns the timestamp |
| 178 | you actually want to know. Also interesting is the combination of |
178 | you actually want to know. Also interesting is the combination of |
| 179 | C<ev_update_now> and C<ev_now>. |
179 | C<ev_now_update> and C<ev_now>. |
| 180 | |
180 | |
| 181 | =item ev_sleep (ev_tstamp interval) |
181 | =item ev_sleep (ev_tstamp interval) |
| 182 | |
182 | |
| 183 | Sleep for the given interval: The current thread will be blocked |
183 | Sleep for the given interval: The current thread will be blocked |
| 184 | until either it is interrupted or the given time interval has |
184 | until either it is interrupted or the given time interval has |
| … | |
… | |
| 1020 | can be done relatively simply by putting mutex_lock/unlock calls around |
1020 | can be done relatively simply by putting mutex_lock/unlock calls around |
| 1021 | each call to a libev function. |
1021 | each call to a libev function. |
| 1022 | |
1022 | |
| 1023 | However, C<ev_run> can run an indefinite time, so it is not feasible |
1023 | However, C<ev_run> can run an indefinite time, so it is not feasible |
| 1024 | to wait for it to return. One way around this is to wake up the event |
1024 | to wait for it to return. One way around this is to wake up the event |
| 1025 | loop via C<ev_break> and C<av_async_send>, another way is to set these |
1025 | loop via C<ev_break> and C<ev_async_send>, another way is to set these |
| 1026 | I<release> and I<acquire> callbacks on the loop. |
1026 | I<release> and I<acquire> callbacks on the loop. |
| 1027 | |
1027 | |
| 1028 | When set, then C<release> will be called just before the thread is |
1028 | When set, then C<release> will be called just before the thread is |
| 1029 | suspended waiting for new events, and C<acquire> is called just |
1029 | suspended waiting for new events, and C<acquire> is called just |
| 1030 | afterwards. |
1030 | afterwards. |
