Just another Perl shrine | |
PerlMonks |
comment on |
( [id://3333]=superdoc: print w/replies, xml ) | Need Help?? |
I've also seen (and commented on) this, but it only happens under special circumstances. Under normal circumstances, with reasonably up-to-date versions of Perl and Time::HiRes and an NT-based version of Windows, you should be getting much better than 1/18 second resolution. On my machine it's in the order of 60 microseconds (1/16666th of a second):
The special circumstances where the low accuracy results show up is under the debugger and in (some) evaled code. Despite spending a lot of time looking at this on 2 separate occasions, I cannot work out why Perl should produce different results under these circumstances. Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
Lingua non convalesco, consenesco et abolesco. -- Rule 1 has a caveat! -- Who broke the cabal?
"Science is about questioning the status quo. Questioning authority".
The "good enough" maybe good enough for the now, and perfection maybe unobtainable, but that should not preclude us from striving for perfection, when time, circumstance or desire allow.
In reply to Re^3: timestamp in milliseconds
by BrowserUk
|
|