On Mon, Dec 19, 2011 at 5:58 PM, Christos Zoulas <chris...@zoulas.com>wrote:
> On Dec 19, 5:00pm, j...@netbsd.org (Julio Merino) wrote: > -- Subject: Re: CVS commit: src/external/bsd/atf/dist/atf-run > > | Interesting; didn't know about these. > | > | But what's the point of this change? It breaks OS X at least and does > not > | fix anything AFAICT. > > I am just trying to use modern POSIX API's to improve portability > Well... modern has come to mean less portable in my book. (I like using modern APIs, but they tend to break grgrgr.) > (and functionality in this case). For example, by using sigevent, > one doesn't need to have global variables and he can pass the struct > he wants to modify in the signal. In addition, one can use the > monotonic clock, which is immune against time changes, and also > use timespec which is more precise. Finally one is not limited to > sigalrm for timers, but can send any signal. Thanks. > I am really suprised > that OS/X does not have them; I would have expected it to work on > more systems than it does currently... I could only check with Snow Leopard and there is no timer_t there. I don't have access to Lion at the moment; when I do, I'll check again. If there is no support in it, I'll have to implement some conditional logic to use the new timers only if available (unless you have a better alternative?). If there is support, then I won't care about backwards compatibility. -- Julio Merino / @jmmv
