What's bugging me though is the values on the right side seem to imply the FMod result should have been 0, but obviously the precision internally is different than what is being shown.
And perhaps the bigger issue is why is the remainder 0.1 - shouldn't it be something really tiny like 1.49012e-08 or something?
I acknowledge that Avisynth is not doing anything technically wrong here - it's just returning whatever C++ says the FMod value is. Which kind of makes it useless - how are we supposed to do a check to ignore really tiny remainders if we're getting such a huge remainder on ones like FMod(0.5,0.1)?
According to this it's expected behaviour, and I tested it in C++ and got the same result as below:
What's bugging me though is the values on the right side seem to imply the FMod result should have been 0, but obviously the precision internally is different than what is being shown.
And perhaps the bigger issue is why is the remainder 0.1 - shouldn't it be something really tiny like 1.49012e-08 or something?
I acknowledge that Avisynth is not doing anything technically wrong here - it's just returning whatever C++ says the FMod value is. Which kind of makes it useless - how are we supposed to do a check to ignore really tiny remainders if we're getting such a huge remainder on ones like FMod(0.5,0.1)?