[datatable-help] Suggestion on ITime class implementing.

[Jim Holtman]

One thing to remember about POSIXct is that with floating point you only have about 15 digits of accuracy.   With 1970 as the base year there are about 12 digits used to get seconds so you only have 3 digits for the subseconds so milliseconds is the limit. 


Sent from my Verizon Wireless 4G LTE Smartphone

-------- Original message --------
From: gaizoule <gaizoule at gmail.com> 
Date: 03/24/2013  07:31  (GMT-05:00) 
To: datatable-help at lists.r-forge.r-project.org 
Subject: Re: [datatable-help] Suggestion on ITime class implementing. 
 
I've met the  same problem which caused by the POSIXct. I think POSIXlt's
storage is wasting a lot of space  and R should support  the intraday time
handling.  Thank you for your useful comments,  I am reading the
StackOverflow.

As for the "Windows could not handle more than milli-second datetimes and
Linux "almost" micros",  this is decided by the OS standard,  not caused by
other thing.  And so,  I think millisecond is enough for me. 



--
View this message in context: http://r.789695.n4.nabble.com/Suggestion-on-ITime-class-implementing-tp4662281p4662322.html
Sent from the datatable-help mailing list archive at Nabble.com.
_______________________________________________
datatable-help mailing list
datatable-help at lists.r-forge.r-project.org
https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/datatable-help
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.r-forge.r-project.org/pipermail/datatable-help/attachments/20130324/aeab216e/attachment.html>