But realistically Y2038 is only an issue if time_t is still a 4 byte int in 2038.
I'm not trying to be a panic monger (lord knows the Y2K 'bug' brought enough of them out of the woodwork!) but the problem is real now. There are plenty of reasons you might want to do a date calculation that went beyond 2038, for example printing a table of predicted values by year for a retirement investment policy, or calculating a mortgage amortisation table, or working out what day of the week to schedule your retirement party :-).
Don't get me wrong, I'm not suggesting these things are impossible or even hard to do. I'm merely saying that the standard tools like time(), localtime() and Time::Local() will let you down. Dave Rolsky's recent article on Perl.com provides some answers.
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:
Outside of code tags, you may need to use entities for some characters:
- 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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||