Big picture...

[Eric S. Raymond]

Hal Murray <hmurray at megapathdsl.net>:
> 
> esr at thyrsus.com said:
> > The most basic requirement for ntp_calendar is that it needs to be able to
> > translate a pivot date to a form that lfp_stamp_to_tspec() can use.
> 
> For that, we can use mktime.  The time zone offset isn't a big deal.  We 
> would probably have to back up by the worst case zone offset so everybody can 
> test right after building.
> 
> If we are using a build time, we can run an external script to generate the 
> date in a convenient format.  date -u +%s looks good to me.

Maybe.  Almost.  How are we going to do this under Windows?  Are we
giving up on a Windows port?  Because POSIX API conformance tells us
we can get at POSIX time froom C, but we have no guarantee that
date(1) will exist.

> Another part for the big picture.
> 
> Except for the l_fp time-stamps in packets, all of the full times are POSIX 
> times. (or should be)

Agreed. Specifically, struct timespecs.
-- 
		<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>

Please consider contributing to my Patreon page at https://www.patreon.com/esr
so I can keep the invisible wheels of the Internet turning. Give generously -
the civilization you save might be your own.