xiph
fix of implicit type conversion.
in casting used in your code, first the result of division is converted to an integer type, with the loss of the fractional part, and then the integer is converted to a floating point type. I think this can be simply fixed.
Apparently the floor fix broke something. Btw, did you consider divinding by 2.0 instead of casting the value?
sorry for the long answer. in fact, division by 2.0 is also a solution. but I recommend using more explicit things that persist after refactoring.) if you insist I will fix it to 2.0.
Note, https://gitlab.xiph.org/xiph/vorbis/ is the upstream project, I've been told the github repository is a convenience copy. Perhaps it is an idea to submit the patch there?
Oh no. I don't have an account there. maybe a better idea would be if you fix the code there yourself. do I close PR?
[ihsinme]
Oh no. I don't have an account there. maybe a better idea would be if you fix the code there yourself. do I close PR?
I am not the maintainer of vorbis, so I do not really have an opinion on this.
-- Happy hacking Petter Reinholdtsen
@ihsinme Thanks for the patches. Can you say a bit more about what issue you're trying to address? Do you think this is a correctness problem? Are you trying to address warnings from a particular compiler?
The appveyor integration test failure is an unrelated issue fixed in 894d1b1f22f2fb8ab6d3aeba863e143416c71ce2. A rebase should complete without error.
@ihsinme Thanks for the patches. Can you say a bit more about what issue you're trying to address? Do you think this is a correctness problem? Are you trying to address warnings from a particular compiler?
the essence of the error is described in PR. this is an integer division, when a fraction is expected.
Just because the assigned variable is floating point doesn't mean the calculations must all be floating point. We are free to choose at what points integer inputs are converted. For example:
- Floating point operations can preserve more precision in calculations.
- Integer operations can be faster than floating point.
- Floating point operations can be faster than checking for integer overflow.
- Division by zero has different results based on the type of the operands.
Which of these criteria are most important varies. That's why I asked what specific issue you wanted to address.