[Date Prev][Date Next][Thread Prev][Thread Next]
- Subject: Re: os.clock() always return 0 on Archlinux (a Linode instance)
- From: David Given <dg@...>
- Date: Tue, 27 Sep 2011 20:14:31 +0100
On 27/09/11 18:01, Peter Cawley wrote:
> os.time - the current time ... or a time representing the date and
> time specified by the given table
Beware, though --- os.time() has a granularity of seconds, so making it
tricky to use for benchmarks. Hence my recommendation of
socket.gettime(), which doesn't.
Just out of interest, has anyone used os.clock() for *anything*, ever?
(Not counting Windows systems where it's equivalent to os.time().)
ââââ ïïïïïïïïïïïïïï âââââ http://www.cowlark.com âââââ
â "Under communism, man exploits man. Under capitalism, it's just the
â opposite." --- John Kenneth Galbrith
Description: OpenPGP digital signature