Not so much a way to fix the code, but a way to fix the program... Document it. If the code is complicated enough to worry about the 2038 issue, then it should be complicated enough to require proper specification and other documents. Add "This code will choke on dates past 2038" (as someone else pointed out, you can hit these bugs well before 2038, if you're calculating dates into the future) If people are aware of this every time they read the docs, it'll make it hard for them to build things on top which will inherit the same problems, and break in difficult to diagnose ways.
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!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
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.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||