Raul wrote:
> ... those floating point numbers are times
> packed as YYYYMMDD.hhmmss
> ...
> Basically: convert to a more compact format
> ...
> An even better approach might be to capture
> that original time stamp as character data,
> rather than using #:
While I recognize that a textual representation may be
best, there may be several advantages to recording
time numerically. It seems to me that when such an
approach is taken Julian dating should be used. I
think 32-bit representation is adequate to support the
fractions-of-a-day required here, but even if it is
not the origin can be adjusted (by approx. 2.45e6
days) to provide plenty of fractional accuracy.
So, my recommendation: Continue to handle temporal
values with floating point, but change to use Julian
dating.
Tracy
____________________________________________________________________________________
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile. Try it now.
http://mobile.yahoo.com/;_ylt=Ahu06i62sR8HDtDypao8Wcj9tAcJ
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
