A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from http://mail.python.org/pipermail/python-dev/2006-August/067879.html below:

[Python-Dev] clock_gettime() vs. gettimeofday()?

[Python-Dev] clock_gettime() vs. gettimeofday()? [Python-Dev] clock_gettime() vs. gettimeofday()?skip at pobox.com skip at pobox.com
Tue Aug 1 20:25:56 CEST 2006 
This has probably been discussed before, however ...

Is there any reason to use clock_gettime() in preference to gettimeofday()
if it exists?  It pretends to at least return seconds + nanoseconds, where
gettimeofday() returns seconds + microseconds.  Are there perhaps some
platforms where it's possible to actually get more useful bits?  On my
Solaris 10/Intel desktop box clock_getres shows 0.01s resolution (not
obviously better) while on a Linux box here it shows 0.001s resolution.  Is
that better than what gettimeofday() does?

Skip
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4