Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 14 Nov 2003 13:41:19 -0600
From:      "Jacques A. Vidrine" <nectar@FreeBSD.org>
To:        freebsd-arch@freebsd.org
Subject:   __TIME_MIN/__TIME_MAX
Message-ID:  <20031114194119.GA94198@madman.celabo.org>

next in thread | raw e-mail | index | archive | help
In at least one place in libc, it is necessary to range check a time_t
value.  One most platforms, time_t has the same range as `int', but
on at least amd64, it has a larger range.  Any objections to adding
definitions of __TIME_MIN and __TIME_MAX to sys/${arch}/_limits.h?

I could just do the usual check for lossage after casting, except that
in theory time_t could be a floating-point value (but not in reality
in FreeBSD).  It seems cleaner to me to have an explicit range.

Cheers,
-- 
Jacques Vidrine   NTT/Verio SME      FreeBSD UNIX       Heimdal
nectar@celabo.org jvidrine@verio.net nectar@freebsd.org nectar@kth.se



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031114194119.GA94198>