Re: Perl -de1 weirdness.

I don't know why you're getting this exact behavior, but given that the debugger does affect the way perl runs (inserting breakpoints and what not into the normal op tree flow) it's not inconceivable that it would throw timing sensitive code off at least a bit.

Comment on Re: Perl -de1 weirdness.

Replies are listed 'Best First'.
Re^2: Perl -de1 weirdness. by BrowserUk (Patriarch) on Jul 19, 2004 at 19:09 UTC
I agree the debugger will likely run the code more slowly, but that means that the values from gettimeofday() should be more widely spaced, not grouped together the way they are. Examine what is said, not who speaks. "Efficiency is intelligent laziness." -David Dunham "Think for yourself!" - Abigail "Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon	[reply]

Replies are listed 'Best First'.

Re^2: Perl -de1 weirdness.
by BrowserUk (Patriarch) on Jul 19, 2004 at 19:09 UTC

I agree the debugger will likely run the code more slowly, but that means that the values from gettimeofday() should be more widely spaced, not grouped together the way they are.

Examine what is said, not who speaks.

"Efficiency is intelligent laziness." -David Dunham
"Think for yourself!" - Abigail
"Memory, processor, disk in that order on the hardware side. Algorithm, algoritm, algorithm on the code side." - tachyon

[reply]