On Apr 7, 7:03 pm, Jamie Wilkinson <[email protected]> wrote: > If time_t was defined as a representation of TAI instead of UTC, it'd > be harder to get it wrong.
Except that TAI is not available until next month and the BIPM recommends against the use of TAI in any real-time system. > Of course then you'd > need a presentation layer to convert TAI into your local human > calendar, but that's pretty simple once the model and view are > separated That exists and it's called zoneinfo and it gets updated all the time as a result of arbitrary and unpredictable human fiat. -- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
