Re: os.clock() always return 0 on Archlinux (a Linode instance)

[David Given <dg@...>]

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

Attachment: signature.asc
Description: OpenPGP digital signature