Re^4: Windows / Linux puzzler

I was able to rule out time as the joker in the deck, if only because we're dealing with an interval of time, not the time of some event. Thus it shouldn't matter if time() returns different values on the two systems.

Comment on Re^4: Windows / Linux puzzler

Replies are listed 'Best First'.
Re^5: Windows / Linux puzzler by swl (Prior) on Mar 24, 2020 at 07:10 UTC
The suggestion by haukex in 11114564 can be followed more thoroughly. Dump each variable and partial step involved in the calculation to track what happens. This means `$min`, `$squelch`, `($min - $squelch)`, and so forth. It is probably worth printing them at a higher precision than the default to see more, e.g. `printf "%.17f\n", ($min - $squelch)` (although both those should be integers based on the original post). Although, "should be integer" depends what you have done with the numbers. Does your code use `$min` or `$squelch` in a floating point context? This could cause them to be used as floats in later calcs. I'm not overly familiar with the internals, though, so cannot say what to expect with any confidence.	[reply] [d/l] [select]

Replies are listed 'Best First'.

Re^5: Windows / Linux puzzler
by swl (Prior) on Mar 24, 2020 at 07:10 UTC

The suggestion by haukex in 11114564 can be followed more thoroughly. Dump each variable and partial step involved in the calculation to track what happens. This means $min, $squelch, ($min - $squelch), and so forth. It is probably worth printing them at a higher precision than the default to see more, e.g. printf "%.17f\n", ($min - $squelch) (although both those should be integers based on the original post).

Although, "should be integer" depends what you have done with the numbers. Does your code use $min or $squelch in a floating point context? This could cause them to be used as floats in later calcs. I'm not overly familiar with the internals, though, so cannot say what to expect with any confidence.

[reply]
[d/l]
[select]