| … | |
… | |
| 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). |
