On Mon, Aug 29, 2016 at 12:32 PM, David Mertz <me...@gnosis.cx> wrote: > In fact, at a certain point I proposed that we should deal with rounding > issues by calling the minimum domain specific time unit an attosecond, and > only use integers in using this unit. That wasn't what was adopted, but it > wasn't absurd. If we had done that, we simply deal with, say 1500 "inherent > units" in the program. The fact it related to a physical quantity is at most > something for documentation (this principle isn't different because we used > floats in this case).
Definitely not absurd. I've done the same kind of thing numerous times (storing monetary values in cents, distances in millimeters, or timepoints in music in milliseconds), because it's just way, WAY simpler than working with fractional values. So the SI prefix gets attached to the (implicit) *unit*, not to the value. I believe this is the correct way to handle things. ChrisA _______________________________________________ Python-ideas mailing list Python-ideas@python.org https://mail.python.org/mailman/listinfo/python-ideas Code of Conduct: http://python.org/psf/codeofconduct/
