Re:9999999999999999.0 – 9999999999999998.0
by Gibbon1 on Saturday January 05, 2019 @02:20PM
(#18833621)
You don't need an exact number but customer data is universally decimal. Soon as you blindly convert that to IEE754 everything is now broken.
[ Parent
| on HN ]
Re:9999999999999999.0 – 9999999999999998.0
by coddingtonbear on Saturday January 05, 2019 @03:44PM
(#18834129)
Is it really, though? I'm honestly struggling to think of a non-currency situation in which fractional customer data necessarily be handled as a decimal value -- and, honestly, even if the availability heuristic might make them seem more common than they are, I'd be astonished if even a single percent of general calculations programmers collectively ask computers to perform are involving currency. Most real-life situations just don't even inherently _have_ that kind of precision, let alone need it. Seriously, I can't think of a time when I've needed to store a coordinate or a person's height as a decimal value to prevent something from being broken.
Re:9999999999999999.0 – 9999999999999998.0
by tedunangst on Saturday January 05, 2019 @08:32PM
(#18835734)
My 5/8s wrench disagrees. Happens to store quite nicely in a float, however.