RE: time_t size: The year 2038 bug?

[David Schwartz]

> Besides, I have yeat to understand what application that would take a high
> preformance kill by having to deal with 64 bit time instead of 32
> bit time.
> Yes, for todays computers it is extra overhead, but not at all at
> the scale
> that when counting all the other zillions of operations normally
> done it would
> really cause a break-or-make case.

	Applications that keep a large number of timestamps in memory. Applications
that sort large amounts of in-memory data by time. Applications that isolate
the time fields from the rest of their records specifically so that large
numbers of them will fit in cache for faster searching and sorting.

	DS