| … | |
… | |
| 124 | this argument. |
124 | this argument. |
| 125 | |
125 | |
| 126 | =head2 TIME REPRESENTATION |
126 | =head2 TIME REPRESENTATION |
| 127 | |
127 | |
| 128 | Libev represents time as a single floating point number, representing |
128 | Libev represents time as a single floating point number, representing |
| 129 | the (fractional) number of seconds since the (POSIX) epoch (somewhere |
129 | the (fractional) number of seconds since the (POSIX) epoch (in practise |
| 130 | near the beginning of 1970, details are complicated, don't ask). This |
130 | somewhere near the beginning of 1970, details are complicated, don't |
| 131 | type is called C<ev_tstamp>, which is what you should use too. It usually |
131 | ask). This type is called C<ev_tstamp>, which is what you should use |
| 132 | aliases to the C<double> type in C. When you need to do any calculations |
132 | too. It usually aliases to the C<double> type in C. When you need to do |
| 133 | on it, you should treat it as some floating point value. Unlike the name |
133 | any calculations on it, you should treat it as some floating point value. |
|
|
134 | |
| 134 | component C<stamp> might indicate, it is also used for time differences |
135 | Unlike the name component C<stamp> might indicate, it is also used for |
| 135 | throughout libev. |
136 | time differences (e.g. delays) throughout libev. |
| 136 | |
137 | |
| 137 | =head1 ERROR HANDLING |
138 | =head1 ERROR HANDLING |
| 138 | |
139 | |
| 139 | Libev knows three classes of errors: operating system errors, usage errors |
140 | Libev knows three classes of errors: operating system errors, usage errors |
| 140 | and internal errors (bugs). |
141 | and internal errors (bugs). |
| … | |
… | |
| 191 | as this indicates an incompatible change. Minor versions are usually |
192 | as this indicates an incompatible change. Minor versions are usually |
| 192 | compatible to older versions, so a larger minor version alone is usually |
193 | compatible to older versions, so a larger minor version alone is usually |
| 193 | not a problem. |
194 | not a problem. |
| 194 | |
195 | |
| 195 | Example: Make sure we haven't accidentally been linked against the wrong |
196 | Example: Make sure we haven't accidentally been linked against the wrong |
| 196 | version. |
197 | version (note, however, that this will not detect ABI mismatches :). |
| 197 | |
198 | |
| 198 | assert (("libev version mismatch", |
199 | assert (("libev version mismatch", |
| 199 | ev_version_major () == EV_VERSION_MAJOR |
200 | ev_version_major () == EV_VERSION_MAJOR |
| 200 | && ev_version_minor () >= EV_VERSION_MINOR)); |
201 | && ev_version_minor () >= EV_VERSION_MINOR)); |
| 201 | |
202 | |
| … | |
… | |
| 1773 | callback (loop, timer, EV_TIMER); |
1774 | callback (loop, timer, EV_TIMER); |
| 1774 | |
1775 | |
| 1775 | And when there is some activity, simply store the current time in |
1776 | And when there is some activity, simply store the current time in |
| 1776 | C<last_activity>, no libev calls at all: |
1777 | C<last_activity>, no libev calls at all: |
| 1777 | |
1778 | |
| 1778 | last_actiivty = ev_now (loop); |
1779 | last_activity = ev_now (loop); |
| 1779 | |
1780 | |
| 1780 | This technique is slightly more complex, but in most cases where the |
1781 | This technique is slightly more complex, but in most cases where the |
| 1781 | time-out is unlikely to be triggered, much more efficient. |
1782 | time-out is unlikely to be triggered, much more efficient. |
| 1782 | |
1783 | |
| 1783 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
1784 | Changing the timeout is trivial as well (if it isn't hard-coded in the |
