<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body ><div>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. </div><div><br></div><div><br></div><div><div style="font-size:75%;color:#575757">Sent from my Verizon Wireless 4G LTE Smartphone</div></div> <br><br><br>-------- Original message --------<br>From: gaizoule <gaizoule@gmail.com> <br>Date: 03/24/2013 07:31 (GMT-05:00) <br>To: datatable-help@lists.r-forge.r-project.org <br>Subject: Re: [datatable-help] Suggestion on ITime class implementing. <br> <br><br>I've met the same problem which caused by the POSIXct. I think POSIXlt's<br>storage is wasting a lot of space and R should support the intraday time<br>handling. Thank you for your useful comments, I am reading the<br>StackOverflow.<br><br>As for the "Windows could not handle more than milli-second datetimes and<br>Linux "almost" micros", this is decided by the OS standard, not caused by<br>other thing. And so, I think millisecond is enough for me. <br><br><br><br>--<br>View this message in context: http://r.789695.n4.nabble.com/Suggestion-on-ITime-class-implementing-tp4662281p4662322.html<br>Sent from the datatable-help mailing list archive at Nabble.com.<br>_______________________________________________<br>datatable-help mailing list<br>datatable-help@lists.r-forge.r-project.org<br>https://lists.r-forge.r-project.org/cgi-bin/mailman/listinfo/datatable-help<br></body>