| … | |
… | |
| 122 | name C<loop> (which is always of type C<ev_loop *>) will not have |
122 | name C<loop> (which is always of type C<ev_loop *>) will not have |
| 123 | this argument. |
123 | this argument. |
| 124 | |
124 | |
| 125 | =head2 TIME REPRESENTATION |
125 | =head2 TIME REPRESENTATION |
| 126 | |
126 | |
| 127 | Libev represents time as a single floating point number, representing the |
127 | Libev represents time as a single floating point number, representing |
| 128 | (fractional) number of seconds since the (POSIX) epoch (somewhere near |
128 | the (fractional) number of seconds since the (POSIX) epoch (somewhere |
| 129 | the beginning of 1970, details are complicated, don't ask). This type is |
129 | near the beginning of 1970, details are complicated, don't ask). This |
| 130 | called C<ev_tstamp>, which is what you should use too. It usually aliases |
130 | type is called C<ev_tstamp>, which is what you should use too. It usually |
| 131 | to the C<double> type in C, and when you need to do any calculations on |
131 | aliases to the C<double> type in C. When you need to do any calculations |
| 132 | it, you should treat it as some floating point value. Unlike the name |
132 | on it, you should treat it as some floating point value. Unlike the name |
| 133 | component C<stamp> might indicate, it is also used for time differences |
133 | component C<stamp> might indicate, it is also used for time differences |
| 134 | throughout libev. |
134 | throughout libev. |
| 135 | |
135 | |
| 136 | =head1 ERROR HANDLING |
136 | =head1 ERROR HANDLING |
| 137 | |
137 | |
