[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index]
[Thread Index]
- Subject: Re: os.clock() always return 0 on Archlinux (a Linode instance)
- From: steve donovan <steve.j.donovan@...>
- Date: Tue, 27 Sep 2011 19:14:11 +0200
On Tue, Sep 27, 2011 at 7:10 PM, Johnson Lin <arch.jslin@gmail.com> wrote:
> socket:settimeout() (however it won't on Windows, works fine.)
That's the problem with os.clock(); it has very different behaviour on
Windows and POSIX systems. One of those little gotchas ;)
steve d.
