|
|
Posted by Colin McKinnon on 04/11/06 00:32
Peter Fox wrote:
> Following on from Michael Vilain's message. . .
>>In article <f3n_f.32362$aa.22902@fe78.usenetserver.com>,
>> "David T. Ashley" <dta@e3ft.com> wrote:
>>
>>> I'm writing a large PHP application that might still be in service in
>>> 2037.
>>>
<snip>
>
> The obvious answer is to decouple your dates from built-in dates of any
> kind (eg by having your own date class) and assume that system clocks
> will be fudged nearer the time. This way your program stays independent
> of all other limitations.
Building your own date handling from scratch seems a bit extravagant.
I often use ISO formatted dates/times (yyyy-mm-dd [hh:mm[:ss]]) and, if I
need to number crunching or change formatting, just pass it over to the
MySQL parser to deal with. I also don't need to worry about whether the
target can calculate negative timestamps, or timestamps before ...erm...
1900ish.
C.
Navigation:
[Reply to this message]
|