| … | |
… | |
| 35 | |
35 | |
| 36 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
36 | *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** |
| 37 | |
37 | |
| 38 | |
38 | |
| 39 | POSIX optionally offers support for a monotonic clock source. EV |
39 | POSIX optionally offers support for a monotonic clock source. EV |
| 40 | can take advantage of this clock source to detect time jumps |
40 | can take advantage of this clock source to detect time jumps more |
| 41 | reliably. Unfortunately, some systems are bound to be broken, so you can |
41 | reliably. Unfortunately, some systems are bound to be broken, so you can |
| 42 | disable this here: you can completely disable the detection and use of |
42 | disable this here: you can completely disable the detection and use of |
| 43 | the monotonic clock by answering 'n' here. Support for this clock type |
43 | the monotonic clock by answering 'n' here. Support for this clock type |
| 44 | will otherwise be autodetected at both compile- and runtime. (this setting |
44 | will otherwise be autodetected at both compile- and runtime. (this setting |
| 45 | currently affects the use of nanosleep over select as well). |
45 | currently affects the use of nanosleep over select as well). |
| … | |
… | |
| 55 | |
55 | |
| 56 | POSIX optionally offers support for a (potentially) high-resolution |
56 | POSIX optionally offers support for a (potentially) high-resolution |
| 57 | realtime clock interface. In a good implementation, using it is faster |
57 | realtime clock interface. In a good implementation, using it is faster |
| 58 | than the normal method of using gettimeofday. Unfortunately, this option |
58 | than the normal method of using gettimeofday. Unfortunately, this option |
| 59 | is also bound to be broken on some systems, and current EV versions do not |
59 | is also bound to be broken on some systems, and current EV versions do not |
| 60 | actually call C<gettimeofday> very often, so ti defaults to no. |
60 | actually call gettimeofday very often, so it defaults to no. |
| 61 | |
61 | |
| 62 | EOF |
62 | EOF |
| 63 | |
63 | |
| 64 | $DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/)); |
64 | $DEFINE .= " -DEV_USE_REALTIME=" . (0 + (prompt ("Prefer clock_gettime (CLOCK_REALTIME) over gettimeofday (y/n)?", "n") =~ /[yY]/)); |
| 65 | |
65 | |
| … | |
… | |
| 146 | won't be used on many platforms, but you can still create your own event |
146 | won't be used on many platforms, but you can still create your own event |
| 147 | loop with kqueue backend if you ask specifically for it. |
147 | loop with kqueue backend if you ask specifically for it. |
| 148 | |
148 | |
| 149 | Here is what we know: |
149 | Here is what we know: |
| 150 | |
150 | |
| 151 | NetBSD: partially working in at least 3.1. Yeah! :) |
151 | NetBSD: partially working in at least 3.1 and later. Yeah! :) |
| 152 | FreeBSD: broken on at least 6.2-STABLE, |
152 | FreeBSD: broken on at least 6.2-STABLE, spotty in later versions, |
| 153 | sockets *likely* work, ptys definitely don't. |
153 | sockets *likely* work, ptys definitely don't. |
| 154 | OpenBSD: reports indicate that it likely doesn't work |
154 | OpenBSD: reports indicate that it likely doesn't work |
| 155 | (similar problems as on FreeBSD). |
155 | (similar problems as on FreeBSD). |
| 156 | OS X: completely, utterly broken on at least < 10.5. |
156 | OS X: completely, utterly broken on at least <= 10.6. |
| 157 | |
157 | |
| 158 | EOF |
158 | EOF |
| 159 | |
159 | |
| 160 | my $can_kqueue = -e "/usr/include/sys/event.h"; |
160 | my $can_kqueue = -e "/usr/include/sys/event.h"; |
| 161 | $can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE}; |
161 | $can_kqueue = $ENV{EV_KQUEUE} if exists $ENV{EV_KQUEUE}; |
