On 26 January 2005 08:43, Ashley Yakeley wrote:
This is one way the time libraries might be organised. I think the functionality splits cleanly into two separate modules.
"Time" module (System.Time? System.DateTime.Time?)
* TAI/UTC arithmetic and conversions, leap-second tables
* possibly UT1 types and conversions, Julian days and dates
* getting the current time
"Date" module (System.Date? System.DateTime.Date?) importing Time module
* time zones
* getting the locale time zone
* converting times to "calendrical" format, Gregorian and possibly also Julian
* calendrical arithmetic e.g. one month after March 31st
* possibly "incomplete dates" e.g. "May 1" for all years
* parsing and showing dates and times
Looks fine to me. Maybe System.Time.Clock and System.Time.Calendar? Cheers, Simon