Re: __TIME_MIN/__TIME_MAX
From: Terry Lambert (tlambert2_at_mindspring.com)
Date: 11/15/03
- Previous message: Harti Brandt: "Re: 64-bit time_t on sparc64, epilogue(?)"
- In reply to: Jacques A. Vidrine: "__TIME_MIN/__TIME_MAX"
- Next in thread: Jacques A. Vidrine: "Re: __TIME_MIN/__TIME_MAX"
- Reply: Jacques A. Vidrine: "Re: __TIME_MIN/__TIME_MAX"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Sat, 15 Nov 2003 14:37:03 -0800 To: "Jacques A. Vidrine" <nectar@FreeBSD.org>
"Jacques A. Vidrine" wrote:
> 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.
XSI: time_t and clock_t shall be integer or real-floating types.
The range should be derived from th type. Defining separate values
outside the implementation namespace might be OK, but keeping those
values synchronized with the size_t is likely to be painful for
years to come.
-- Terry
_______________________________________________
freebsd-arch@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-arch
To unsubscribe, send any mail to "freebsd-arch-unsubscribe@freebsd.org"
- Previous message: Harti Brandt: "Re: 64-bit time_t on sparc64, epilogue(?)"
- In reply to: Jacques A. Vidrine: "__TIME_MIN/__TIME_MAX"
- Next in thread: Jacques A. Vidrine: "Re: __TIME_MIN/__TIME_MAX"
- Reply: Jacques A. Vidrine: "Re: __TIME_MIN/__TIME_MAX"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
