Just as a more general note:
When we program using dates and times here in the office, we almost never deal in date strings except for output purposes. Internally, everything is done using "seconds since the epoch"-type timestamps (the value returned by time() is an example) and then common modules are used to convert from these timestamps into strings. Even if you can't install these modules (which, really, you should at least convince your boss to install either Time::ParseDate or Date::Manip), you can do most of the work yourself using localtime(). The only place that becomes hairy is when you're dealing with daylight savings time.
Seriously consider ditching the whole 30Nov00 way of passing dates around in your script query string and replace it with the timestamp for that date. For one, '00' isn't Y2K compliant, and two, you'll have a common format you can use for addition, comparison, and conversion.
-
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.
|
