News for hackers. Stuff that matters.
Re:Bisecting Floating Point Numbers by zurn on Tuesday November 10, 2015 @01:28AM (#10537891)
Floating point is actually a significant source of bugs in 3D graphics and games. And a complex thing you have to constantly keep in mind, taking cognitive resources from other more useful stuff. And a thing you have to code around, increasing the codebase complexity, making changes harder and taking time from programming/debugging/testing useful code.

CPUs and GPUs do have support for fixed point (aka integer) data formats, it's been a DX/OpenGL requirement for a while. Though I don't know what API issues you run into if you try to avoid FP altogether.

Re:Bisecting Floating Point Numbers by shele on Tuesday November 10, 2015 @03:59AM (#10538239)
Floating point arithmetic is a significant source of bugs. And if you transition to fixed point arithmetic, you will still have a significant source of same-same-but-different bugs (maybe unless you really only need to add things and not never scale or multiply them).
Re:Bisecting Floating Point Numbers by zurn on Wednesday November 11, 2015 @12:28AM (#10544974)
What kind of bugs do you have in mind for fixed point?

While there no doubt would be some, I have a feeling they are a significantly lesser drag (in frequency and debugging complexity) than floating point bugs. Assuming the language supports fixed point.

Of course you can imagine error-prone fixed point too. Writing shaders with plain integers while trying to manually keep track heterogenous fixed point scales would be a nightmare for example...