Le 2014-09-09 12:19, Luca Barbato a écrit :
On 09/09/14 10:01, Rémi Denis-Courmont wrote:
Why would it be more robust? Unless the libc is utterly broken, the
result will be the same. Indeed I believe glibc's sysconf() calls
clock_getres() internally.
Why would be unavailable? Is it possible to disable it at runtime?
On Linux, that would mean ancient kernel.
Generally speaking, whatever.
--
Rémi Denis-Courmont
_______________________________________________
libav-devel mailing list
[email protected]
https://lists.libav.org/mailman/listinfo/libav-devel
