[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: parse-duration.c - TIME_MAX 2038 unpreparedness

From: Bruce Korb
Subject: Re: parse-duration.c - TIME_MAX 2038 unpreparedness
Date: Sat, 14 Jun 2014 14:31:44 -0700
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130922 Icedove/17.0.9

On 06/10/14 17:49, Jim Meyering wrote:
Why impose such a limit?
I'd go with TYPE_MAXIMUM (time_t).

a) because I do not read BASH headers (or any other headers) for fun.
   Unless I get bumped somehow, I don't know about such things, and

b) like I said, if anybody on the planet really needs a time difference
   in excess of 68 years, I'd be mightily surprised.

Now that I know about TYPE_MAXIMUM, I'll use it, sure.

Meanwhile, please be re-assured that in the soon-to-come 24 years from now,
an unmodified parse-duration will not choke.  :)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]