> A 32-bit integer divided into a 16-bit whole and a 16-bit fraction would be limited to only representing values between -32768 and 32767 while also having wor

> A 32-bit integer divided into a 16-bit whole and a 16-bit fraction would be limited to only representing values between -32768 and 32767 while also having worse precision than a 32-bit ieee std754 floating-point at values near 0 ...OK? I'm not sure how that relates to my supposition that trigonometric operations are likely to be more common in 3D modelling cases. I'm not arguing for or against any particular representation of numbers therein. > Representing money in terms of cents instead of dollars removes the need for real-numbers entirely I wasn't imagining dollars-and-cents, but rather rates - X per Y, the most natural way in which division arises in real life. > Most computer programs don't need real numbers of any sort... You're again arguing against a case I'm not making. I'm not making any claims about the necessity (or otherwise) of real numbers in programs, but simply wondering about the prevalence of particular operations. > and the ones that do need to be written by people who understand basic mathematical concepts like precision. A snide insult motivated by your own misunderstanding of my point. I understand precision, and it's irrelevant to my point.