Date: Mon, 29 Oct 2001 02:32:20 +1100 (EST) From: Bruce Evans <bde@zeta.org.au> To: Bernd Walter <ticso@cicely8.cicely.de> Cc: Matthew Dillon <dillon@apollo.backplane.com>, <arch@FreeBSD.ORG> Subject: Re: illegal &time_t useage in /usr/src Message-ID: <20011029022409.P3648-100000@delplex.bde.org> In-Reply-To: <20011028113509.A48670@cicely8.cicely.de>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sun, 28 Oct 2001, Bernd Walter wrote:
> What about struct timespec and struct timeval?
> There is no functional need to have long defined tv_nsec and tv_usec
> fields as long as no spec says so.
Specs do say so. timespec is { time_t tv_sec; long tv_nsec; }
(POSIX.1-1996). timeval is { time_t tv_sec; suseconds_t tv_usec; }
(draft POSIX.1-200x). suseconds_t is a signed integer type capable
of storing values at least in the range [-1, 1000000].
So you can change the type of tv_usec (but shouldn't, because it is
specified to be long by old defacto standards), but you can't change
tv_nsec (and neither can standards, because it is specified to be long
by old standards).
Bruce
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20011029022409.P3648-100000>