|
My concern is probably not as great as I originally thought. Losing 1
second because of truncation of seconds is probably not all that bad.
If I'm losing 1 second after 10 days or 1 day, that's not all that bad.
The program is not to be a cure all for clock drift. I guess I was alarmed that I might get into a situation where 2.7 would represented as 2, 4, 6, 8, ... as 2.7 was "added" to seconds for each 24 hours passed the base. However, I'm recalculating based on multiplication and not addition, so the times would be 2, 5 (2.7*2), 7 (2.7*3), ... 27 (2.7*10 and not 20), ... Kent Johnson wrote: On Wed, Sep 10, 2008 at 8:13 PM, Wayne Watson <[EMAIL PROTECTED]> wrote: --
Wayne Watson (Watson Adventures, Prop., Nevada City, CA)
(121.015 Deg. W, 39.262 Deg. N) GMT-8 hr std. time)
Obz Site: 39° 15' 7" N, 121° 2' 32" W, 2700 feet
"If voting made any difference they wouldn't let us do it."
-- Mark Twain
Web Page: <www.speckledwithstars.net/>
|
_______________________________________________ Tutor maillist - [email protected] http://mail.python.org/mailman/listinfo/tutor
