I don't think you need to worry. Sure, in current day programs, time() is a 32 bit integer. But it needn't be. Even if today it was implemented, not using a 64 bit integer but using a (double) float instead of an integer, you'd have a precision of 53 bits. Surely that would be enough.
And I really don't see a reason why the epoch couldn't just stay the same, Jan 1 1970 00:00:00 GMT. In other words: I don't really expect code like yours to break, provided your Perl port will be upgraded by then — and, as Abigail wrote, your system can handle it. Honestly, I do expect that that will turn out to be the biggest problem: timestamps on file systems.
In reply to Re: 2038 bug
in thread 2038 bug
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||