Time Libraries Rough Draft

Gregory Wright gwright at comcast.net
Wed Feb 9 12:32:34 EST 2005

On Feb 9, 2005, at 6:24 AM, Ashley Yakeley wrote:

> This seems to be roughly where we're at with the time libraries. It's
> now three modules, Clock, LeapSeconds, and Calendar. Most people will
> have no need for LeapSeconds.
> I've added two more things which haven't been discussed much. The first
> is a getCPUTime function that returns the current "CPU time". This has
> an arbitrary base, but it doesn't hiccup. The Unix interface for this 
> is
> a "clock()" function that returns time in some unit, and
> CLOCKS_PER_SECOND, which is a constant to convert to seconds. I'm
> assuming there's a Windows equivalent to this.
> The second thing is a type-synonym of Rational for Julian dates. Julian
> dates are a standard representation of UT1, where one unit is one day,
> and UT1 is a good choice for representing Earth-based times in the far
> past or future continuously.

Are the Julian Dates to be true Julian dates (date changes at noon) or
Modified Julian Dates (changes at midnight)?


More information about the Libraries mailing list