TAI-based non-POSIX time_t

[John Cowan]

Markus Kuhn scripsit:

> Reason 2: Local-time errors affect critical long-term state such as
> file-system timestamps much less, as these tend to be in UTC. (Just
> an hour ago, we discovered a machine that had its default time zone
> set to US East Coast local time instead of London local time. We were
> able to fix that problem on-the-fly without any disruption, as most
> system state remained unaffected. The machine knew UTC accurately
> to within 2 ms all the time.)

Then again, there was my colleague's Windows system, which was still
running on Redmond time instead of New York time.  Unfortunately,
we couldn't fix it, because the thousands of appointments, past and
future, that he had stored in Outlook's calendar would then all be
off by three hours.

Consequently, his email tended to arrive from the future.

-- 
It was dreary and wearisome.  Cold clammy winter still held way in this
forsaken country.  The only green was the scum of livid weed on the dark
greasy surfaces of the sullen waters.  Dead grasses and rotting reeds loomed
up in the mists like ragged shadows of long-forgotten summers.
        --"The Passage of the Marshes"          http://www.ccil.org/~cowan