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.
the hatter
In reply to Re: 2038 bug
by hatter
in thread 2038 bug
by toma
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|
