Craig Berry wrote: > > On Wednesday, October 01, 2008, at 03:13PM, "Michael G Schwern" <[EMAIL > PROTECTED]> wrote: > >>> EAGLE> cc check_max/define=__SIGNED_INT_TIME_T >>> EAGLE> link check_max >>> EAGLE> run check_max >>> gmtime max 2147483647 >>> localtime max 2147483647 >>> gmtime min 3221225472 >>> localtime min 3221225472 >> Well that's unsettling. Any ideas? > > My guess (without the code in front of me) is it's a negative number but your > not allowing it to be stored/displayed that way.
That edition of check_max had a bug introduced by an attempted optimization (don't ask why I'm optimizing configure probes) which would account for the crazy results. It would fail when time_t over/underflowed at a much larger absolute value than the date functions fail, which is what happens on VMS with a signed time_t. -- Whip me, beat me, make my code compatible with VMS!
