Re^3: In search of a bug in Time::HiRes on Windows.

It looks like the problem went away, yes. Unfortunately, I don't remember how to reproduce the original problem. If I run into it again I'll let you know.

In the debugger I get:

  DB<2> print time  . $/ for 1 .. 20;;
1118999589.19879
1118999589.2088
1118999589.2088
1118999589.21882
1118999589.21882
1118999589.22883
1118999589.23884
1118999589.23884
1118999589.24886
1118999589.24886
1118999589.25887
1118999589.26889
1118999589.26889
1118999589.2789
1118999589.2789
1118999589.28892
1118999589.29893
1118999589.30894
1118999589.30894
1118999589.31896

Comment on Re^3: In search of a bug in Time::HiRes on Windows.

Replies are listed 'Best First'.

Re^4: In search of a bug in Time::HiRes on Windows.
by BrowserUk (Patriarch) on Jun 17, 2005 at 09:26 UTC

This is weird! I consistantly get lo res results in the debugger?

  DB<2> print time . $/ for 1 .. 20;;
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.44888
1119000264.48013
1119000264.48013
1119000264.48013
1119000264.48013
1119000264.48013
1119000264.48013
1119000264.49575
1119000264.49575
1119000264.49575
[download]

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.

[reply]
[d/l]


"be consistent"
	PerlMonks