by worker201 » Mon Aug 14, 2006 2:57 pm
What I meant was that the first guy who stored a binary floating point number must have seen the issue. I don't know, I guess I would have scrapped that method then and tried to figure out something that works.
If that hadn't been done, then the methods to get around it ought to have been coded into the OS, or the language headers. It just seems like the sort of thing a modern programmer wouldn't have to deal with, just because somebody would have found a way to deal with it already. A simple floating point calculation should be an abstraction of whatever arithmetic method this guy suggests for minimizing float errors.
I admit to not reading the solutions page (or the deep tech page), but I did understand why certain numbers are difficult/impossible to accurately represent with current binary floating point procedures.