What you don’t get, Benoit, is that forcing the result into an integer is precisely what creates the wrong result. Using round to correct that is computing la Shaddock : I compute wrong, and then I use round to make it right. That is no way to code.
Look at the code I posted. It is exactly your code, with only one difference : instead of cramming the result into an integer which truncates the value into 71, I simply put the result into a double, and it is correct.
Mathematics are an exact science. You don’t accommodate approximately. You think you found a solution because in you very limited example, round seems to produce the correct result. Sure, with 3.6 or even 3.65 it seems to do. But what is the first term is 3.69 ? Then the exact result is 73.8, not 74.
You are free to code wrong, of course. But then don’t file bug reports for bugs you created yourself.