Learn how easy it is to sync an existing GitHub or Google Code repo to a SourceForge project! See Demo
I'd have thought a real floating point type would be better -- the distance calculations certainly require floating point, and if the data were floating point to begin with, that would save conversion horsepower.
Is it just that people have a lot of uses (and of course avoiding floating point for anything *except* floating point calculations is a good principle)? Or am I missing something?
(Gee, this forum sure seems to be busy).