Do we need a few new types?

Gary E. Miller gem at rellim.com
Fri Mar 10 21:51:08 UTC 2017


Yo Hal!

On Fri, 10 Mar 2017 13:44:29 -0800
Hal Murray <hmurray at megapathdsl.net> wrote:

> POSIX has time_t
> ntp_types.h has time64_t
> 
> There are various places that are working with seconds since NTP
> epoch.  They are using uint32_t and uint64_t.
> 
> I think we want something like ntp_time32_t and ntp_time64_t.

Or, just go with the flow and use the epoch in a timepec like
structure:

ntp_time_t {
	int epoch;
	uint32 seconds;
        uint32 faction;
}

That would stop all that shifting back and forth.

We need timespec for getting and setting the system clock, some
similar keep s my brain fro having to shift as much.

It will be less important as we get rid of more things using l_fp for
no good reason.

> I think we will also want come better names/aliases for things like
> lfpuint

Yeah. x and y make sense when typing at 100 baud, but not now.

RGDS
GARY
---------------------------------------------------------------------------
Gary E. Miller Rellim 109 NW Wilmington Ave., Suite E, Bend, OR 97703
	gem at rellim.com  Tel:+1 541 382 8588

	    Veritas liberabit vos. -- Quid est veritas?
    "If you can’t measure it, you can’t improve it." - Lord Kelvin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <https://lists.ntpsec.org/pipermail/devel/attachments/20170310/ecd27c26/attachment.bin>


More information about the devel mailing list