OK. Good point.
Note that that article was written 4 years ago
when R was at version 1.9 and POSIXt did not fully support
subseconds. At that time, POSIXct could represent subseconds
internally but it was not used as POSIXlt did not yet support it
and that and the associated digits.sec option
Hi Gabo,
FAQ 7.31 does not apply to this. numeric in R is 64bit which is large eno=
ugh to handle this.
I
figured out the cause is that Sys.time() gives millisecond value while
b-as.POSIXct(format(a,tz=3DGMT)) cuts off that part.=20
Then of course a-b is not 5 hours!
Do it again with
Yea I thought that would be the story behind it. Thanks.
Date: Sun, 17 Feb 2008 16:15:27 -0500
From: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: Re: [Rd] Arithmetic bug? (found when use POSIXct) (PR#10776)
CC: [EMAIL PROTECTED]
OK. Good point.
Note that that article was written
Full_Name: Bo Zhou
Version: 2.6.1 (2007-11-26)
OS: Windows XP
Submission from: (NULL) (207.237.54.242)
Hi,
I found an arithmetic problem when I'm doing something with POSIXct
The code to reproduce it is as follows (This is the recommended way of finding
out time zone difference on R News 2004-1
See FAQ 7.31 or explain what you believe to be the problem.
On Feb 16, 2008 1:05 PM, [EMAIL PROTECTED] wrote:
Full_Name: Bo Zhou
Version: 2.6.1 (2007-11-26)
OS: Windows XP
Submission from: (NULL) (207.237.54.242)
Hi,
I found an arithmetic problem when I'm doing something with POSIXct
