| 1 |
On 2017-07-14 08:15, Andrew Tselischev wrote: |
| 2 |
> On Fri, Jul 14, 2017 at 08:42:01PM +0700, Vadim A. Misbakh-Soloviov wrote: |
| 3 |
> >> when time_t reaches 2 billion. |
| 4 |
> > |
| 5 |
> > He meant 2k38 problem, when time_t will overflow int32 :) |
| 6 |
> |
| 7 |
> I would bet that somewhere there is a quick-job shell script that parses |
| 8 |
> unix timestamps with regular expressions and assumes they start with a 1. :D |
| 9 |
> |
| 10 |
Why do I feel that we've already gone through at least one upgrade of "Unix Time" already. I'm not sure if it was something like going from int16 to int32, or more that it went from signed int32 to unsigned int32. |
| 11 |
|
| 12 |
Jigme Datse Yli-Rasku |
| 13 |
|
| 14 |
-- |
| 15 |
Jigme Datse Yli-Rasku |
| 16 |
jigme.datse@×××××××××××××××.com (Preferred address for new messages) |
| 17 |
|
| 18 |
Jigme Datse Yli-Rasku |
| 19 |
PO Box 270 |
| 20 |
Rossland, BC V0G 1Y0 |
| 21 |
Canada |
| 22 |
|
| 23 |
....................................................................... |
| 24 |
... This message should be electronically signed, and if the sender ... |
| 25 |
... has your public key, may also be encrypted. ... |
| 26 |
... If you have any questions about this, please email, or call. ... |
| 27 |
....................................................................... |
Archives